Dear Chairs & WG, I support advancing it.
Public IPv4 in 4over6 is a useful use case, especially for the operators who still have plenty of reserved public IPv4 addresses. The architecture is simple, and the v4 address provision is different from the other 4over6 solutions, so it is quite reasonable to make it as an independent standard track. All the best Bing > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Suresh Krishnan > Sent: Monday, December 17, 2012 12:34 PM > To: Softwires WG > Cc: Yong Cui; Ralph Droms > Subject: [Softwires] Second working group last call for > draft-ietf-softwire-public-4over6-04 > > Hi all, > This message starts a second softwire working group last call on > advancing the draft about providing Public IPv4 over IPv6 Access Network > as a Standards Track RFC. The authors believe that this version has > addressed the issues raised during the previous WGLC. The draft > is available at > > http://www.ietf.org/id/draft-ietf-softwire-public-4over6-04.txt > http://tools.ietf.org/html/draft-ietf-softwire-public-4over6-04 > > Substantive comments and statements of support/opposition for advancing > this document should be directed to the mailing list. Editorial > suggestions can be sent directly to the authors. The chairs will send in > their comments as well during the last call period. This last call will > conclude on January 4, 2013. > > Regards, > Suresh & Yong > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
