Hi, Steve,
Thanks for the quick response.
DSCPs. Guidelines for mixing traffic-types within a PCN-domain
are given in [I-D.ietf-pcn-marking-behaviour].
o Any packet that is not-PCN but which shares the same Diffserv
codepoint as PCN-enabled traffic MUST have the ECN field of its
outermost IP header equal to 00.
Spencer (minor): this is the only point in the specification (that I
can
find) that makes reference to the "outermost IP header". I'm not sure
whether to suggest s/outermost// here or to ask that a statement be
added
earlier in the document to clearly state that PCN encoding only
protects
inelastic traffic when it's used for the outermost IP header, but the
current text seems to call attention to this in a way that makes the
reader
wonder what is special about THIS requirement that isn't true of the
other
requirements listed.
I'm sorry, but I'm having a hard time following this comment. Could you
please clarify?
I'm probably not saying this well - my question is basically why this
requirement calls out "ECN field of its outermost IP header", when other
requirements that mention ECN field do not. If there's a reason why
s/outermost// in this case would be wrong, I don't know what it is, and
that's what worries me - should the other requirements ALSO say "outermost"?
I'm not asking for this change, just trying to understand.
Thanks,
Spencer
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art