I really like this idea. What worries me is the different cases to be examined/solved depending on the source device: host (applications) or router (protocols). And this draft takes into account mostly the first.
-- Tassos Ronald Bonica wrote on 20/06/2013 18:55: > Folks, > > Please review this draft and provide comments. > > Ron > > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> Sent: Thursday, June 20, 2013 11:48 AM >> To: Ronald Bonica >> Subject: New Version Notification for draft-bonica-6man-frag-deprecate- >> 00.txt >> >> >> A new version of I-D, draft-bonica-6man-frag-deprecate-00.txt >> has been successfully submitted by Ron Bonica and posted to the IETF >> repository. >> >> Filename: draft-bonica-6man-frag-deprecate >> Revision: 00 >> Title: IPv6 Fragment Header Deprecated >> Creation date: 2013-06-20 >> Group: Individual Submission >> Number of pages: 7 >> URL: http://www.ietf.org/internet-drafts/draft-bonica-6man- >> frag-deprecate-00.txt >> Status: http://datatracker.ietf.org/doc/draft-bonica-6man- >> frag-deprecate >> Htmlized: http://tools.ietf.org/html/draft-bonica-6man-frag- >> deprecate-00 >> >> >> Abstract: >> This memo deprecates the IPv6 Fragment Header. It provides reasons >> for deprecation and updates RFC 2460. >> >> >> >> >> >> The IETF Secretariat >> >> > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
