Hi Lucy, > -----Original Message----- > From: Lucy yong [mailto:[email protected]] > Sent: Wednesday, April 29, 2015 11:15 AM > To: Templin, Fred L; Tom Herbert > Cc: [email protected]; [email protected] > Subject: RE: [Int-area] Why combine IP-in-UDP with GUE? > > Hi Fred, > > Change the GUE header to treat the first nibble as a next header selector. 4 > means IPv4, 6 means IPv6 and X means GUE. > [Lucy] As I mentioned in several previous mails, I don't think that this is a > good design for GUE. Even if a compression is required, the > solution SHOULD use a separate UDP port to indicate IP first and then check > the first nibble for IPv4 or IPv6, which, in fact, is the IP-in- > UDP proposal.
I will say again that the IP-in-UDP proposal as it stands does not have a solution for tunnel fragmentation (made available by GUE). > However I agree with Tom that the compression concept does not align with GUE > principal. GUE encapsulation should not assume IP > payload in first place! The proposed solution does not assume IP; it assumes a next header selector in the first nibble of the data following the UDP header. Non IP can be conveyed when the next header selector indicates GUE. Thanks - Fred [email protected] > Regards, > Lucy > > > > Thanks - Fred > [email protected] > > > Tom > > > > > Thanks - Fred > > > [email protected] > > > > > >> Tom > > >> > > >> > Thanks - Fred > > >> > [email protected] > > >> > > > >> >> Lucy > > >> >> > > >> >> Thanks - Fred > > >> >> [email protected] > > >> >> > > >> >> > However, if GUE payload is > > >> >> > IP, it is OK to inspect the first nibble of the payload to > > >> >> > determine IPv4 or IPv6 because this aligns with IP protocol. > > >> >> > > > >> >> > Thanks, > > >> >> > Lucy > > >> >> > > > >> >> > - Stewart > > >> >> > > > >> >> > > > >> >> > > > >> >> > _______________________________________________ > > >> >> > Int-area mailing list > > >> >> > [email protected] > > >> >> > https://www.ietf.org/mailman/listinfo/int-area > > >> >> > > > >> >> > _______________________________________________ > > >> >> > Int-area mailing list > > >> >> > [email protected] > > >> >> > https://www.ietf.org/mailman/listinfo/int-area > > >> > > > >> > _______________________________________________ > > >> > Int-area mailing list > > >> > [email protected] > > >> > https://www.ietf.org/mailman/listinfo/int-area _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
