Hi, This makes sense to me. I totally agree. If I might suggest a minor change.., I would add in section 3 the text "section 4" after RFC 5952 [RFC5952]:
--- RFC 5952 [RFC5952] section 4 recommends to use the compressed format for IPv6 address textual representation. For instance, leading zeros MUST be suppressed, the use of the symbol "::" MUST be used to its maximum capability and the characters "a", "b", "c", "d", "e", and "f" in an IPv6 address MUST be represented in lowercase. -- Regards, Alejandro, El 4/6/2016 a las 7:23 AM, Andrei Robachevsky escribió: > Hi, > > I recently submitted an I-D > draft-robachevsky-mandating-use-of-ipv6-examples-00.txt, mandating use > of IPv6 in examples in RFCs. > > I was reading some pretty recent drafts and noticed that authors > continue using IPv4 in their examples. This is probably more convenient, > but is not really forward thinking. Also, the prevalence of IPv6 > examples will send a strong message that IPv4 is essentially a legacy > protocol. > > I wonder if this WG is interested in progressing this document as a WG > item. > > Thanks, > > Andrei > > >> Name: draft-robachevsky-mandating-use-of-ipv6-examples >> Revision: 00 >> Title: Mandating use of IPv6 in examples >> Document date: 2016-03-21 >> Group: Individual Submission >> Pages: 3 >> URL: >> https://www.ietf.org/internet-drafts/draft-robachevsky-mandating-use-of-ipv6-examples-00.txt >> Status: >> https://datatracker.ietf.org/doc/draft-robachevsky-mandating-use-of-ipv6-examples/ >> Htmlized: >> https://tools.ietf.org/html/draft-robachevsky-mandating-use-of-ipv6-examples-00 >> >> >> Abstract: >> IPv6 is a successor of the legacy IPv4 protocol. This document >> mandates use of IPv6 in examples provided in RFCs. > > > _______________________________________________ > sunset4 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/sunset4
_______________________________________________ sunset4 mailing list [email protected] https://www.ietf.org/mailman/listinfo/sunset4
