Re: [PCN] New Version Notificationfordraft-ietf-pcn-baseline-encoding-01

{ The key section for the WG to note is Appendix B where I have put in a
{ couple of questions that I would welcome input on.
{ 
{ The first of these is where to put the text (now set out as a table)
about
{ valid and invalid transitions at PCN nodes? Should this be part of the
{ baseline encoding or should it be split between a new edge node
behaviour
{ document and Phil's marking behaviour.

My view is that this should be in the encoding drafts, as what
transitions are valid depends on the encoding (eg the answer would be
different for PSDM). However, I also think - since other encodings are
seen as extensions of the baseline encoding - that the baseline should
define what 'extensions' means - it presumably means that there are
restrictions on those other encodings in terms of what transitions are
valid, eg that 11 MUST correspond to some kind of PCN-marking. 

{ 
{ The second question relates to how to best handle the unexpected
presence
{ of the EXP codepoint. There is a potential for this to happen during
any
{ partial deployment of an experimental encoding extension scheme.
Whilst it
{ would be best for an operator to ensure all nodes run the same
encoding
{ there is a chance this might not happen. The best solution as I see it
is
{ for the baseline scheme to treat EXP the same as NM but to raise a
{ management alarm...

I think this is reasonable. 

{ 
{ I have also highlighted another point in Appendix A which needs a
{ decision: should we as a WG recommend that RFC3168 full functionality
{ tunnels SHOULD NOT be used in a PCN-domain or would it be better to
put
{ our collective voices behind Bob's attempts to correct the anomalous
{ behaviour of tunnels which he is currently trying to push through
TSVWG
{ (draft-briscoe-tsvwg-ecn-tunnel-01)

'should we recommend...' - don't know.
'should we put our collective voices..' - yes. 

_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn