Hi Tom,
I read this draft. It is interesting proposal. It is indeed another tunneling
encapsulation proposal and aims in applying to NVO as well (not limited to).
Regarding the semantics, it suggests using the flag on the header to indicate
the option field presence in the header. Three flags are specified in current
proposal. For such kinds of semantics, IMO, it is very important to specify the
processing order in the flags that derives the option field presence. This is
because that these optional fields are present independently. If the flag is
on, the corresponding field present, but the processor does not know where the
option fields present. If all the option field length is vary, it mandates that
the processor look at the header flag in the order too. Therefore, specifying
flag processing order is required in such semantics.
For the same above reason, the statement "A middle box may interpret some flags
and optional fields of the GUE
header for classification purposes, but is not required to understand all flags
and fields in GUE packets." has some problem. How does middle box know where
the needed fields present on the GUE packets without knowing all the flows and
option fields format? I do not know why you want middle box to perform the
treatment on the inner payload without tunnel termination?
It is my impression that IPsec maybe used by a underlay network that carries
NVO traffic when necessary. Here you proposal that using IPsec within the
overlay network. Does that mean that the overlay app. does not rely on the
underlay network to provide security?
o Type: type of header. The rest of the fields in the header are
defined based the type.
Do you mean here? a typo?
The proposal of encapsulating a layer 2 protocol in GUE is interesting. It
means that, for different protocol type value, GUE header may be different. Why
do you think that is a good design? How can hardware implement in an easy way?
Regards,
Lucy
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
