[mpls] Comment resolution on MPLS Identifiers draft

[George Swallow <[e-mail]>]

Addressed a comment from Mach Chen on the need for two LSP-IDs for
associated bi-directional LSPs.  Added a new section which allows for two
LSP-IDs in this case, as well as a mapping to RSVP-TE signaling.

Removed the automatic mapping of tunnel numbers to IF_IDs as this is
implementation specific.

Addressed the ITU comments as follows:


1.  Not accepted.  The sentence is correct as it is.  It does not say
    that the document defines all identifier nor does it mention LSPs,
    tunnels or connections.

2.  Accepted

3.  Accepted in principle - removed sentence.  Note that the TLV
    definitions are what actually define the order.

4.  Accepted

5.  Added the Operator ID.  However the divergent naming of endpoint
    was not added.  Such a move would add a great deal of complexity.
    Need to see clear market demand before adding.

6.  Accepted in principle - wording is diffent since some of the
    changes propose are to a direct quote from another RFC.

7.  The Global_ID is not an ASN.  A non-zero Global_ID MUST be derived
    from an ASN owned by the operator.  In a node running both MPLS-TP
    and BGP the ASN and the Global_ID could have the same value.  But
    the ASN could be another ASN also owned by the operator.

8.  Accepted

9.  Accepted with wording changes.  In particular the comment is
    addressed in a new paragraph immediately after the paragraph
    where the comment was made.

10. Accepted

11. Accepted with wording changed.

12. Accepted

13. Accepted

14. Accepted in principle.  The comment was addressed by making a
    reference to hierarchical tunnels in the last paragraph of section
    4.

15. Accepted

16. Accepted

17, 18. Paragraph rewritten for clarification.

19. Accepted

20. Per comment 26, this text was not moved.

21. Accepted but used East/West instead of A/Z

22. This has been stable text for over a year and half.  We see no
    point in changing it now.

23. Type-o fixed

24. This is the naming for co-routed bi-directional tunnels.  See new
    text in section xx for associated bi-directional

25. This is an artifact cause by the type-o which was addressed per comment
23.

26. Accepted.  Added text on associated bi-directional.

27. Type-o fixed

28. Type-o fixed

29. Accepted, text added.

30. Accepted but used East/West instead of A/Z

31. Not accepted.  The PW_ID is not unique to a node, but to a node
    pair.  To automatically generate MEP_IDs in this case would
    require both node_ids and both global_ids for global uniqueness.
    Further, having another option just makes for more complication.

32. Accepted but used East/West instead of A/Z

33. The AGI is used in defining L2VPNs

34. Rather than incorporating the comment, the note was removed as it
    was not really appropriate for this document.

35. Not accepted.  Believe the existing text is clear enough.  The
    MEP-ID is required and there are two defined.  This document does
    not specify usage.

36. Accepted with wording changes - new text is "where the Node_ID is
    the node in which the MEP is located and the AC_ID is the AC_ID of
    the Pseudowire at that node."

37. Changed name to Pseudowire Segments Endpoint ID or PW_SE_ID

38. Type-o fixed

39. Accepted