| < draft-wu-pce-dns-pce-discovery-08.txt | draft-wu-pce-dns-pce-discovery-09.txt > | |||
|---|---|---|---|---|
| PCE Working Group Q. Wu | PCE Working Group Q. Wu | |||
| Internet-Draft D. Dhody | Internet-Draft D. Dhody | |||
| Intended status: Standards Track Huawei | Intended status: Experimental Huawei | |||
| Expires: October 31, 2015 D. King | Expires: June 8, 2016 D. King | |||
| Lancaster University | Lancaster University | |||
| D. Lopez | D. Lopez | |||
| Telefonica I+D | Telefonica I+D | |||
| J. Tantsura | J. Tantsura | |||
| Ericsson | Ericsson | |||
| April 29, 2015 | December 6, 2015 | |||
| Path Computation Element (PCE) Discovery using Domain Name System(DNS) | Path Computation Element (PCE) Discovery using Domain Name System(DNS) | |||
| draft-wu-pce-dns-pce-discovery-08 | draft-wu-pce-dns-pce-discovery-09 | |||
| Abstract | Abstract | |||
| Discovery of the Path Computation Element (PCE) within an IGP area or | Discovery of the Path Computation Element (PCE) within an IGP area or | |||
| routing domain is possible using OSPF and IS-IS IGP discovery. | routing domain is possible using OSPF and IS-IS IGP discovery. | |||
| However, it has been established that in certain deployment scenarios | However, it has been established that in certain deployment scenarios | |||
| PCEs may not wish, or be able to participate within the IGP process. | PCEs may not wish, or be able to participate within the IGP process. | |||
| In those scenarios, it is beneficial for the Path Computation Client | In those scenarios, it is beneficial for the Path Computation Client | |||
| (PCC) (or other PCE) to discover PCEs via an alternative mechanism to | (PCC) (or other PCE) to discover PCEs via an alternative mechanism to | |||
| using an IGP discovery. | using an IGP discovery. | |||
| skipping to change at page 1, line 46 ¶ | skipping to change at page 1, line 46 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| 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." | |||
| This Internet-Draft will expire on October 31, 2015. | This Internet-Draft will expire on June 8, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 9, line 29 ¶ | skipping to change at page 9, line 29 ¶ | |||
| particular realm, the PCC or other PCEs has to know in advance the | particular realm, the PCC or other PCEs has to know in advance the | |||
| search path of the resolver, i.e.,in which realm to look for a PCE, | search path of the resolver, i.e.,in which realm to look for a PCE, | |||
| and in which Application Identifier it is interested. | and in which Application Identifier it is interested. | |||
| The search path of the resolver can either be pre-configured, or | The search path of the resolver can either be pre-configured, or | |||
| discovered using Diameter, DHCP or other means. For example, the | discovered using Diameter, DHCP or other means. For example, the | |||
| realm could be deduced from the Network Access Identifier (NAI) in | realm could be deduced from the Network Access Identifier (NAI) in | |||
| the User-Name attribute-value pair (AVP) or extracted from the | the User-Name attribute-value pair (AVP) or extracted from the | |||
| Destination-Realm AVP in Diameter [RFC6733]. | Destination-Realm AVP in Diameter [RFC6733]. | |||
| When pre-configuration is used, PCE domain(e.g.,AS200)can be added as | When pre-configuration is used, PCE domain(e.g.,AS200)may be added as | |||
| "subdomains" of the first-level domain of the underlying service | "subdomains" of the first-level domain of the underlying service | |||
| (e.g., AS200.example.com), which allows a NAPTR query for a server in | (e.g., AS200.example.com), which allows a NAPTR query for a server in | |||
| a PCE domain associated with DNS domain-name. | a PCE domain associated with DNS domain-name. | |||
| When DHCP is used, it SHOULD know the domain-name of that realm and | When DHCP is used, it SHOULD know the domain-name of that realm and | |||
| use DHCP to discover IP address of the PCE in that realm that | use DHCP to discover IP address of the PCE in that realm that | |||
| provides path computation service along with some PCE location | provides path computation service along with some PCE location | |||
| information useful to a PCC (or other PCE) for a PCE selection, and | information useful to a PCC (or other PCE) for a PCE selection, and | |||
| contact it directly. In some instances, the discovery may result in | contact it directly. In some instances, the discovery may result in | |||
| a per protocol/application list of domain-names that are then used as | a per protocol/application list of domain-names that are then used as | |||
| skipping to change at page 15, line 51 ¶ | skipping to change at page 15, line 51 ¶ | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", March 1997. | Requirement Levels", March 1997. | |||
| [RFC2782] Gulbrandsen, A., "A DNS RR for specifying the location of | [RFC2782] Gulbrandsen, A., "A DNS RR for specifying the location of | |||
| services (DNS SRV)", RFC 2782, February 2000. | services (DNS SRV)", RFC 2782, February 2000. | |||
| [RFC3397] Aboba, B., "Dynamic Host Configuration Protocol (DHCP) | [RFC3397] Aboba, B., "Dynamic Host Configuration Protocol (DHCP) | |||
| Domain Search Option", RFC 3397, November 2002. | Domain Search Option", RFC 3397, November 2002. | |||
| [RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS) | [RFC3403] Mealling, M., "Dynamic Delegation Discovery System (DDDS) | |||
| Part Three: The Domain Name System (DNS) Database", RFC | Part Three: The Domain Name System (DNS) Database", | |||
| 3403, October 2002. | RFC 3403, October 2002. | |||
| [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host | [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host | |||
| Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, | Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, | |||
| December 2003. | December 2003. | |||
| [RFC3958] Daigle, D. and A. Newton, "Domain-Based Application | [RFC3958] Daigle, D. and A. Newton, "Domain-Based Application | |||
| Service Location Using SRV RRs and the Dynamic Delegation | Service Location Using SRV RRs and the Dynamic Delegation | |||
| Discovery Service (DDDS)", RFC 3958, January 2005. | Discovery Service (DDDS)", RFC 3958, January 2005. | |||
| [RFC4033] Arends, R., "DNS Security Introduction and Requirements", | [RFC4033] Arends, R., "DNS Security Introduction and Requirements", | |||
| skipping to change at page 16, line 34 ¶ | skipping to change at page 16, line 34 ¶ | |||
| [BGP-LS] Gredler, H., "North-Bound Distribution of Link-State and | [BGP-LS] Gredler, H., "North-Bound Distribution of Link-State and | |||
| TE Information using BGP", ID draft-ietf-idr-ls- | TE Information using BGP", ID draft-ietf-idr-ls- | |||
| distribution-10, January 2015. | distribution-10, January 2015. | |||
| [RFC1464] Rosenbaum, R., "Using the Domain Name System To Store | [RFC1464] Rosenbaum, R., "Using the Domain Name System To Store | |||
| Arbitrary String Attributes", RFC 1464, May 1993. | Arbitrary String Attributes", RFC 1464, May 1993. | |||
| [RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 | [RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 | |||
| Signature Option", RFC 2385, August 1998. | Signature Option", RFC 2385, August 1998. | |||
| [RFC2845] Vixie, P., Gudmundsson, O., Eastlake, D., and B. | [RFC2845] Vixie, P., Gudmundsson, O., Eastlake 3rd, D., and B. | |||
| Wellington, "Secret Key Transaction Authentication for DNS | Wellington, "Secret Key Transaction Authentication for DNS | |||
| (TSIG)", RFC 2845, May 2000. | (TSIG)", RFC 2845, DOI 10.17487/RFC2845, May 2000, | |||
| <http://www.rfc-editor.org/info/rfc2845>. | ||||
| [RFC2930] Eastlake, D., "Secret Key Establishment for DNS (TKEY | [RFC2930] Eastlake 3rd, D., "Secret Key Establishment for DNS (TKEY | |||
| RR)", RFC 2930, September 2000. | RR)", RFC 2930, DOI 10.17487/RFC2930, September 2000, | |||
| <http://www.rfc-editor.org/info/rfc2930>. | ||||
| [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | |||
| Element (PCE)-Based Architecture", RFC 4655, August 2006. | Element (PCE)-Based Architecture", RFC 4655, August 2006. | |||
| [RFC4674] Droms, R., "Requirements for Path Computation Element | [RFC4674] Droms, R., "Requirements for Path Computation Element | |||
| (PCE) Discovery", RFC 4674, December 2003. | (PCE) Discovery", RFC 4674, December 2003. | |||
| [RFC4927] Le Roux, JL., "Path Computation Element Communication | [RFC4927] Le Roux, JL., "Path Computation Element Communication | |||
| Protocol (PCECP) Specific Requirements for Inter-Area MPLS | Protocol (PCECP) Specific Requirements for Inter-Area MPLS | |||
| and GMPLS Traffic Engineering", RFC 4927, June 2007. | and GMPLS Traffic Engineering", RFC 4927, June 2007. | |||
| [RFC5088] Le Roux, JL., "OSPF Protocol Extensions for Path | [RFC5088] Le Roux, JL., "OSPF Protocol Extensions for Path | |||
| Computation Element (PCE) Discovery", RFC 5088, January | Computation Element (PCE) Discovery", RFC 5088, January | |||
| 2008. | 2008. | |||
| [RFC5089] Le Roux, JL., "IS-IS Protocol Extensions for Path | [RFC5089] Le Roux, JL., "IS-IS Protocol Extensions for Path | |||
| Computation Element (PCE) Discovery", RFC 5089, January | Computation Element (PCE) Discovery", RFC 5089, January | |||
| 2008. | 2008. | |||
| [RFC5152] Vasseur, JP., Ayyangar, A., and R. Zhang, "A Per-Domain | [RFC5152] Vasseur, JP., Ed., Ayyangar, A., Ed., and R. Zhang, "A | |||
| Path Computation Method for Establishing Inter-Domain | Per-Domain Path Computation Method for Establishing Inter- | |||
| Traffic Engineering (TE) Label Switched Paths (LSPs)", RFC | Domain Traffic Engineering (TE) Label Switched Paths | |||
| 5152, February 2008. | (LSPs)", RFC 5152, DOI 10.17487/RFC5152, February 2008, | |||
| <http://www.rfc-editor.org/info/rfc5152>. | ||||
| [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax | [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax | |||
| Specifications: ABNF", STD 68, RFC 5234, January 2008. | Specifications: ABNF", STD 68, RFC 5234, | |||
| DOI 10.17487/RFC5234, January 2008, | ||||
| <http://www.rfc-editor.org/info/rfc5234>. | ||||
| [RFC5376] Bitar, N., "Inter-AS Requirements for the Path Computation | [RFC5376] Bitar, N., "Inter-AS Requirements for the Path Computation | |||
| Element Communication Protocol (PCECP)", RFC 5376, | Element Communication Protocol (PCECP)", RFC 5376, | |||
| November 2008. | November 2008. | |||
| [RFC5441] Vasseur, JP., Zhang, R., Bitar, N., and JL. Le Roux, "A | [RFC5441] Vasseur, JP., Ed., Zhang, R., Bitar, N., and JL. Le Roux, | |||
| Backward-Recursive PCE-Based Computation (BRPC) Procedure | "A Backward-Recursive PCE-Based Computation (BRPC) | |||
| to Compute Shortest Constrained Inter-Domain Traffic | Procedure to Compute Shortest Constrained Inter-Domain | |||
| Engineering Label Switched Paths", RFC 5441, April 2009. | Traffic Engineering Label Switched Paths", RFC 5441, | |||
| DOI 10.17487/RFC5441, April 2009, | ||||
| <http://www.rfc-editor.org/info/rfc5441>. | ||||
| [RFC5452] Hubert, A., "Measures for Making DNS More Resilient | [RFC5452] Hubert, A., "Measures for Making DNS More Resilient | |||
| against Forged Answers", RFC 5452, January 2009. | against Forged Answers", RFC 5452, January 2009. | |||
| [RFC5557] Lee, Y., Le Roux, JL., King, D., and E. Oki, "Path | [RFC5557] Lee, Y., Le Roux, JL., King, D., and E. Oki, "Path | |||
| Computation Element Communication Protocol (PCEP) | Computation Element Communication Protocol (PCEP) | |||
| Requirements and Protocol Extensions in Support of Global | Requirements and Protocol Extensions in Support of Global | |||
| Concurrent Optimization", RFC 5557, July 2009. | Concurrent Optimization", RFC 5557, DOI 10.17487/RFC5557, | |||
| July 2009, <http://www.rfc-editor.org/info/rfc5557>. | ||||
| [RFC5671] Yasukawa, S. and A. Farrel, "Applicability of the Path | [RFC5671] Yasukawa, S. and A. Farrel, Ed., "Applicability of the | |||
| Computation Element (PCE) to Point-to-Multipoint (P2MP) | Path Computation Element (PCE) to Point-to-Multipoint | |||
| MPLS and GMPLS Traffic Engineering (TE)", RFC 5671, | (P2MP) MPLS and GMPLS Traffic Engineering (TE)", RFC 5671, | |||
| October 2009. | DOI 10.17487/RFC5671, October 2009, | |||
| <http://www.rfc-editor.org/info/rfc5671>. | ||||
| [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. | [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. | |||
| Cheshire, "Internet Assigned Numbers Authority (IANA) | Cheshire, "Internet Assigned Numbers Authority (IANA) | |||
| Procedures for the Management of the Service Name and | Procedures for the Management of the Service Name and | |||
| Transport Protocol Port Number Registry", BCP 165, RFC | Transport Protocol Port Number Registry", BCP 165, | |||
| 6335, August 2011. | RFC 6335, DOI 10.17487/RFC6335, August 2011, | |||
| <http://www.rfc-editor.org/info/rfc6335>. | ||||
| [RFC6408] Jones, M., Korhonen, J., and L. Morand, "Diameter | [RFC6408] Jones, M., Korhonen, J., and L. Morand, "Diameter | |||
| Straightforward-Naming Authority Pointer (S-NAPTR) Usage", | Straightforward-Naming Authority Pointer (S-NAPTR) Usage", | |||
| RFC 6408, November 2011. | RFC 6408, DOI 10.17487/RFC6408, November 2011, | |||
| <http://www.rfc-editor.org/info/rfc6408>. | ||||
| [RFC6457] Takeda, T., "PCC-PCE Communication and PCE Discovery | [RFC6457] Takeda, T., "PCC-PCE Communication and PCE Discovery | |||
| Requirements for Inter-Layer Traffic Engineering", RFC | Requirements for Inter-Layer Traffic Engineering", | |||
| 6457, June 2007. | RFC 6457, June 2007. | |||
| [RFC6781] Kolkman, O., Mekking, W., and R. Gieben, "DNSSEC | [RFC6781] Kolkman, O., Mekking, W., and R. Gieben, "DNSSEC | |||
| Operational Practices, Version 2", RFC 6781, December | Operational Practices, Version 2", RFC 6781, December | |||
| 2012. | 2012. | |||
| [RFC6805] King, D. and A. Farrel, "The Application of the Path | [RFC6805] King, D. and A. Farrel, "The Application of the Path | |||
| Computation Element Architecture to the Determination of a | Computation Element Architecture to the Determination of a | |||
| Sequence of Domains in MPLS and GMPLS", RFC 6805, November | Sequence of Domains in MPLS and GMPLS", RFC 6805, November | |||
| 2012. | 2012. | |||
| [RFC7025] Otani, T., "Requirements for GMPLS Applications of PCE", | [RFC7025] Otani, T., "Requirements for GMPLS Applications of PCE", | |||
| RFC 7025, September 2013. | RFC 7025, September 2013. | |||
| [RFC7399] Farrel, A. and D. King, "Unanswered Questions in the Path | [RFC7399] Farrel, A. and D. King, "Unanswered Questions in the Path | |||
| Computation Element Architecture", RFC 7399, October 2014. | Computation Element Architecture", RFC 7399, | |||
| DOI 10.17487/RFC7399, October 2014, | ||||
| <http://www.rfc-editor.org/info/rfc7399>. | ||||
| [STATEFUL-PCE] | [STATEFUL-PCE] | |||
| Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP | Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP | |||
| Extensions for Stateful PCE", ID draft-ietf-pce-stateful- | Extensions for Stateful PCE", ID draft-ietf-pce-stateful- | |||
| pce-11, April 2015. | pce-11, April 2015. | |||
| Authors' Addresses | Authors' Addresses | |||
| Qin Wu | Qin Wu | |||
| Huawei | Huawei | |||
| End of changes. 18 change blocks. | ||||
| 33 lines changed or deleted | 46 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||