Re: Brian Haberman's Discuss on draft-ietf-xmpp-6122bis-23: (with DISCUSS)
Peter Saint-Andre - &yet <[email protected]> Wed, 10 Jun 2015 13:28:47 -0600
| Newsgroups | gmane.ietf.xmpp |
|---|---|
| Message-ID | <[email protected]> |
On 6/10/15 1:27 PM, Brian Haberman wrote: > Hi Peter, > > On 6/10/15 2:07 PM, Peter Saint-Andre - &yet wrote: > >>> I agree that a proper reference to 6874 would be useful. Is there any >>> need to mention the potential for a literal to include the zone id? >> >> How is this text? >> >> ### >> >> domainpart = IP-literal / IPv4address / ifqdn >> ; >> ; the "IPv4address" and "IP-literal" rules are >> ; defined in RFC 3896 and RFC 6874 respectively, >> ; and the first-match-wins (a.k.a. "greedy") >> ; algorithm described in Appendix B of RFC 3986 >> ; applies to the matching process >> >> <snip/> >> >> Implementation Note: Reuse of the IP-literal rule from [RFC6874] >> implies that IPv6 addresses are enclosed in square brackets (i.e., >> beginning with '[' and ; ending with ']'), which was not the case >> with the definition of the XMPP address format in [RFC3920] but >> which was changed in [RFC6122]. Also note that the IP-literal >> rule was updated between RFC 3986 and RFC 6874 to optionally add a >> zone identifier to any literal address. >> >> ### >> > > This all works for me. Thanks for the quick response and turn around! Great. I'll post a revised I-D after the telechat. Peter