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

[<philip.eardley at bt.com>]

{ 1. Provide marking and encoding drafts as generic building blocks. An
{ additional document explains how they are used in a specific
deployment
{ scenario. There may be one deployment scenario or more, depending on
{ whether a single one covers all needs. The current objective of the
{ group is to define one deployment scenario and keep the door open for
{ others just in case the one does not satisfy the application
scenarios.
{ That's at least my understanding.
{ 
{ 2. Provide marking and encoding drafts as parts of a specific
deployment
{ scenario. This degrades readability of the documents and prevents
simple
{ extension of PCN since the building blocks are not generic and must be
{ changed to describe alternative deployment scenarios.
{ 
{ Currently I see that the second path is taken because the marking
draft
{ contains a lot deployment specific assumptions. I don't know whether
{ this happened intentionally or not.
{ 

this wasn't intentional on my part. But I know this is something that I
have to make an effort to avoid, so would appreciate it if you could
point out places where the marking draft makes deployment specific
assumptions. Yes I agree the text in S2.5 does. App C also, but this
Appendix will be deleted in the next version (it's basically a reminder
to the WG that we seem to need a PDB doc, and we need someone to write
it (not me!))

thanks
phil
_______________________________________________
PCN mailing list
PCN at ietf.org
https://www.ietf.org/mailman/listinfo/pcn