draft-ietf-pce-p2mp-req-01.txt   draft-ietf-pce-p2mp-req-02.txt 
Network Working Group S. Yasukawa Network Working Group S. Yasukawa
Internet Draft NTT Internet Draft NTT
Category: Informational A. Farrel (Ed.) Category: Informational A. Farrel
Created: February 13, 2009 Old Dog Consulting Created: August 20, 2009 Old Dog Consulting
Expires: August 13, 2009 Expires: February 20, 2010
PCC-PCE Communication Requirements for Point to Multipoint PCC-PCE Communication Requirements for Point to Multipoint
Multiprotocol Label Switching Traffic Engineering (MPLS-TE) Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
draft-ietf-pce-p2mp-req-01.txt draft-ietf-pce-p2mp-req-02.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with the
the provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
skipping to change at page 3, line 27 skipping to change at page 3, line 25
path. path.
2.1.2. Indication of P2MP Objective Functions 2.1.2. Indication of P2MP Objective Functions
[RFC4657] includes the requirement to be able to specify the [RFC4657] includes the requirement to be able to specify the
objective functions to be applied by a PCE during path computation. objective functions to be applied by a PCE during path computation.
This document makes no change to that requirement, but it should be This document makes no change to that requirement, but it should be
noted that new and different objective functions will be used for noted that new and different objective functions will be used for
P2MP computation. Definitions for core objective functions can be P2MP computation. Definitions for core objective functions can be
found in [PCE-OF] together with usage procedures. New objective found in [RFC5541] together with usage procedures. New objective
functions for use with P2MP path computations will need to be functions for use with P2MP path computations will need to be
defined and allocated codepoints in a separate document. defined and allocated codepoints in a separate document.
2.1.3. Non-Support of P2MP Path Computation 2.1.3. Non-Support of P2MP Path Computation
PCEs are not required to support P2MP path computation. Therefore, it PCEs are not required to support P2MP path computation. Therefore, it
MUST be possible for a PCE to reject a P2MP Path Computation Request MUST be possible for a PCE to reject a P2MP Path Computation Request
message with a reason code that indicates no support for P2MP path message with a reason code that indicates no support for P2MP path
computation. computation.
skipping to change at page 10, line 27 skipping to change at page 10, line 27
[RFC4875] Aggarwal, R., Papadimitriou, D., and Yasukawa, S., [RFC4875] Aggarwal, R., Papadimitriou, D., and Yasukawa, S.,
"Extensions to Resource Reservation Protocol - Traffic "Extensions to Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) for Point-to-Multipoint TE Label Engineering (RSVP-TE) for Point-to-Multipoint TE Label
Switched Paths (LSPs)", RFC 4875, May 2007. Switched Paths (LSPs)", RFC 4875, May 2007.
[RFC5073] Vasseur, J.P, and Le Roux, J.L., Editors, "IGP Routing [RFC5073] Vasseur, J.P, and Le Roux, J.L., Editors, "IGP Routing
Protocol Extensions for Discovery of Traffic Protocol Extensions for Discovery of Traffic
Engineering Node Capabilities", RFC 5073, December Engineering Node Capabilities", RFC 5073, December
2007. 2007.
[PCE-OF] Le Roux, J.L., Vasseur, J.P., and Lee, Y., "Encoding [RFC5541] Le Roux, J.L., Vasseur, J.P., and Lee, Y., "Encoding
of Objective Functions in Path Computation Element of Objective Functions in the Path Computation Element
communication Protocol (PCEP)", draft-ietf-pce-of, Communication Protocol (PCEP)", RFC 5541, June 2009.
work in progress.
8. Authors' Addresses 8. Authors' Addresses
Seisho Yasukawa Seisho Yasukawa
NTT Corporation (R&D Strategy Department) NTT Corporation
3-1, Otemachi 2-Chome Chiyodaku, Tokyo 100-8116 Japan 9-11, Midori-Cho 3-Chome
Email: s.yasukawa@hco.ntt.co.jp Musashino-Shi, Tokyo 180-8585,
Japan
Email: yasukawa.seisho@lab.ntt.co.jp
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
9. Intellectual Property Statement 9. Full Copyright Statement
The IETF Trust takes no position regarding the validity or scope of
any Intellectual Property Rights or other rights that might be
claimed to pertain to the implementation or use of the technology
described in any IETF Document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights.
Copies of Intellectual Property disclosures made to the IETF
Secretariat and any assurances of licenses to be made available, or
the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
any standard or specification contained in an IETF Document. Please
address the information to the IETF at ietf-ipr@ietf.org.
The definitive version of an IETF Document is that published by, or
under the auspices of, the IETF. Versions of IETF Documents that are
published by third parties, including those that are translated into
other languages, should not be considered to be definitive versions
of IETF Documents. The definitive version of these Legal Provisions
is that published by, or under the auspices of, the IETF. Versions of
these Legal Provisions that are published by third parties, including
those that are translated into other languages, should not be
considered to be definitive versions of these Legal Provisions.
For the avoidance of doubt, each Contributor to the IETF Standards
Process licenses each Contribution that he or she makes as part of
the IETF Standards Process to the IETF Trust pursuant to the
provisions of RFC 5378. No language to the contrary, or terms,
conditions or rights that differ from or are inconsistent with the
rights and licenses granted under RFC 5378, shall have any effect and
shall be null and void, whether published or posted by such
Contributor, or included with or in such Contribution.
10. Full Copyright Statement
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
All IETF Documents and the information contained therein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
 End of changes. 9 change blocks. 
59 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/