draft-ietf-pce-interas-pcecp-reqs-02.txt   draft-ietf-pce-interas-pcecp-reqs-03.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Verizon Verizon
Internet Draft Raymond Zhang Internet Draft Raymond Zhang
(Editor) (Editor)
BT Infonet BT Infonet
Intended Status: Informational Kenji Kumaki Intended Status: Informational Kenji Kumaki
(Editor) (Editor)
KDDI Corporation KDDI Corporation
Inter-AS Requirements for the Path Computation Element Inter-AS Requirements for the Path Computation Element
Communication Protocol (PCECP) Communication Protocol (PCECP)
draft-ietf-pce-interas-pcecp-reqs-02.txt draft-ietf-pce-interas-pcecp-reqs-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author By submitting this Internet-Draft, each author
represents that any applicable patent or other IPR represents that any applicable patent or other IPR
claims of which he or she is aware have been or will claims of which he or she is aware have been or will
be disclosed, and any of which he or she becomes aware be disclosed, and any of which he or she becomes aware
will be disclosed, in accordance with Section 6 of BCP will be disclosed, in accordance with Section 6 of BCP
79. 79.
skipping to change at page 10, line 42 skipping to change at page 10, line 42
communication among inter-AS PCEs and other PCEs in a single SP communication among inter-AS PCEs and other PCEs in a single SP
administrative domain as well among inter-AS PCEs under different SP administrative domain as well among inter-AS PCEs under different SP
administrative domains. [RFC4657] specifies requirements on PCECP to administrative domains. [RFC4657] specifies requirements on PCECP to
protect against spoofing, snooping and DoS attacks. These protect against spoofing, snooping and DoS attacks. These
requirements become especially critical in the multi-AS case. requirements become especially critical in the multi-AS case.
Additionally, two aspects of operations specific to inter-AS PCEs Additionally, two aspects of operations specific to inter-AS PCEs
require careful security considerations. There are two modes of require careful security considerations. There are two modes of
determining peering PCEs across the AS boundary manual determining peering PCEs across the AS boundary manual
configuration and auto-discovery. In the manual mode, mechanisms configuration and auto-discovery. In the manual mode, mechanisms
for securely exchanging authentication keys across SP boundaries for securely exchanging manually confgiured authentication key or
MUST be defined. For example, PCE registration MAY be served as a key sets across SP boundaries MUST be defined. For example, the
mechanism for securely exchanging authentication keys across SP authentication key May be manually configured for each PCE peer and
boundaries. In the auto-discovery mode, inter-as PCEs can be auto- PCE registration MAY be served as a mechanism for securely
discovered only if it is configured to participate in that discovery exchanging authentication keys across SP boundaries. In the
scope. An inter-AS PCE is not necessarily able to establish PCEP auto-discovery mode, inter-as PCEs can be auto-discovered only if
sessions with the discovered PCEs in its scope(s), it MUST be able it is configured to participate in that discovery scope.
to authenticate with the peering inter-AS PCE, therefore mechanisms
An inter-AS PCE is not necessarily able to establish PCEP sessions
with the discovered PCEs in its scope(s), it MUST be able to
authenticate with the peering inter-AS PCE, therefore mechanisms
for securely exchanging authentication keys across SP boundaries for securely exchanging authentication keys across SP boundaries
MUST also be defined in this case. Furthermore, the auto-discovery MUST also be defined in this case. Furthermore, the auto-discovery
process itself MUST also be authenticated. process itself MUST also be authenticated.
6. IANA Considerations 6. IANA Considerations
This document makes no requests for IANA action. This document makes no requests for IANA action.
7. Acknowledgments 7. Acknowledgments
 End of changes. 2 change blocks. 
9 lines changed or deleted 12 lines changed or added

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