The MPLS WG Archive

[Eric Rosen <erosen@cisco.com>]

These minutes are so selective in  what they include and what they omit that
I think it would be better to have  no minutes at all than to leave these as
the official record of the meeting. 

>  There are issues in that the  IETF Standards Process (RFC 2999) says that
>  a normative reference in a Draft  Standard can't point to a document that
>  is "only" a Proposed Standard.  The LDP specification is dependent on the
>  MPLS  Architecture  (RFC  3031)  that  is still  Proposed  Standard.  The
>  suggested remedy  here is  to included enough  of the of  the information
>  that is  reference directly  in the LDP  specification and then  move the
>  reference to Informational. 

The minutes  should capture the remarks  that this is a  stupid idea because
(a) including  one document in another  to avoid a reference  is a generally
bad strategy for producing a coherent  document set, and (b) one cannot move
a document to informational when it is the only place that specifies much of
the operation of the technology. 

> 7. T-MPLS; report from the IETF liaison to ITU-T SG15

The minutes seem to omit any  mention of the entire discussion that followed
Adrian's presentation.

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls