The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2004-Dec> msg00031



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] draft-ietf-mpls-p2mp-sig-requirement-00.txt

  • From: "Thomas D. Nadeau" <tnadeau@cisco.com>
  • Date: Tue, 21 Dec 2004 11:12:51 -0500
  • Cc: mpls@ietf.org, Monique Morrow <mmorrow@cisco.com>


On Dec 21, 2004, at 8:44 AM, Loa Andersson wrote:

> Monique, Tom and doc authors,
>
> I'm not sure it is good style putting requirements on
> other documents (in this case in part from the same working
> group in a requirement document. The document is intended to
> become an RFC and if we have requirements on what goes into
> other RFCs it will be hard to follow, especially after that
> stuff has been put into that document.
>
> Would be better to state something like "The MPLS and GMPLS
> MIB will be / has been enhanced to provide P2MP TE LSP
> management."

	This sounds like a reasonable approach as long as the
remaining text in the section is removed (as it doesn't seem
to belong, nor does it fit with your recommendation).

> Please note that when you write this, you also commit to be
> part of making it happen. So do that foot work (get
> someone to edit the enhancements) before submitting.

	I have long committed to doing this sort of stuff. *)

	--Tom


>
> /Loa
>
> Monique Morrow wrote:
>
>> I support this recommendation Tom -- this would be most efficent.
>> /monique
>> On 21/12/04 7:27 am, "Thomas D. Nadeau" <tnadeau@cisco.com> wrote:
>>> I have a comment on draft-ietf-mpls-p2mp-sig-requirement-00.txt.
>>> The paragraph below seems to on the one hand, have no
>>> requirements as is stated in the last paragraph, does
>>> give a requirement. I suggest that this document simply
>>> refer to draft-ietf-mpls-oam-requirements-05.txt, since the WG
>>> agreed to include all MPLS OAM-related requirements in
>>> this draft.
>>>
>>> --Tom
>>>
>>>
>>> 4.18 P2MP MPLS OAM
>>>
>>>    Management of P2MP LSPs is as important as the management of P2P
>>>    LSPs.
>>>
>>>    The MPLS and GMPLS MIB modules MUST be enhanced to provide P2MP TE
>>>    LSP management.
>>>
>>>    In order to facilitate correct management, P2MP TE LSPs MUST have
>>>    unique identifiers.
>>>
>>>    OAM facilities will have special demands in P2MP environments
>>>    especially within the context of tracing the paths and 
>>> connectivity
>>>    of P2MP TE LSPs. The precise requirements and mechanisms for OAM 
>>> are
>>>    out of the scope of this document. It is expected that a separate
>>>    document will cover these requirements.
>>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@lists.ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls mailing list
>> mpls@lists.ietf.org
>> https://www1.ietf.org/mailman/listinfo/mpls
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                            loa@pi.se
>

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