rfc7622v1.txt		rfc7622.txt
	skipping to change at page 7, line 7		skipping to change at page 7, line 7
	during preparation of a string for inclusion in a domainpart slot.		during preparation of a string for inclusion in a domainpart slot.
	In addition, the string MUST be encoded as UTF-8 [RFC3629].		In addition, the string MUST be encoded as UTF-8 [RFC3629].
	3.2.2. Enforcement		3.2.2. Enforcement
	An entity that performs enforcement in XMPP domainpart slots MUST		An entity that performs enforcement in XMPP domainpart slots MUST
	prepare a string as described in Section 3.2.1 and MUST also apply		prepare a string as described in Section 3.2.1 and MUST also apply
	the normalization, case-mapping, and width-mapping rules defined in		the normalization, case-mapping, and width-mapping rules defined in
	[RFC5892].		[RFC5892].
	The order in which the rules are applied for IDNA2008 (see		Informational Note: The order in which the rules are applied for
	[RFC5892] and [RFC5895]) is different from the order for		IDNA2008 (see [RFC5892] and [RFC5895]) is different from the order
	localparts and resourceparts as described under Sections 3.3		for localparts and resourceparts as described under Sections 3.3
	and 3.4.		and 3.4.
	3.2.3. Comparison		3.2.3. Comparison
	An entity that performs comparison of two strings before or after		An entity that performs comparison of two strings before or after
	their inclusion in XMPP domainpart slots MUST prepare each string as		their inclusion in XMPP domainpart slots MUST prepare each string as
	specified in Section 3.2.1 and then enforce the normalization,		specified in Section 3.2.1 and then enforce the normalization,
	case-mapping, and width-mapping rules specified in Section 3.2.2.		case-mapping, and width-mapping rules specified in Section 3.2.2.
	The two strings are to be considered equivalent if they are an exact		The two strings are to be considered equivalent if they are an exact
	octet-for-octet match (sometimes called "bit-string identity").		octet-for-octet match (sometimes called "bit-string identity").
	skipping to change at page 14, line 49		skipping to change at page 14, line 49
	[RFC3921] [XEP-0016] when the value of the 'type' attribute is		[RFC3921] [XEP-0016] when the value of the 'type' attribute is
	"jid".		"jid".
	o The 'jid' attribute of the <item/> element for Service Discovery		o The 'jid' attribute of the <item/> element for Service Discovery
	defined in [XEP-0030].		defined in [XEP-0030].
	o The <value/> element for Data Forms [XEP-0004] when the 'type'		o The <value/> element for Data Forms [XEP-0004] when the 'type'
	attribute is "jid-single" or "jid-multi".		attribute is "jid-single" or "jid-multi".
	o The 'jid' attribute of the <conference/> element for Bookmark		o The 'jid' attribute of the <conference/> element for Bookmark
	storage [XEP-0048].		Storage [XEP-0048].
	o The <JABBERID/> of the <vCard/> element for vCard 3.0 [XEP-0054]		o The <JABBERID/> of the <vCard/> element for vCard 3.0 [XEP-0054]
	and the <uri/> child of the <impp/> element for vCard 4.0		and the <uri/> child of the <impp/> element for vCard 4.0
	[XEP-0292] when the XML character data identifies an XMPP URI		[XEP-0292] when the XML character data identifies an XMPP URI
	[RFC5122].		[RFC5122].
	o The 'from' attribute of the <delay/> element for Delayed Delivery		o The 'from' attribute of the <delay/> element for Delayed Delivery
	[XEP-0203].		[XEP-0203].
	o The 'jid' attribute of the <item/> element for the Blocking		o The 'jid' attribute of the <item/> element for the Blocking
End of changes. 2 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/