idnits 2.17.1 draft-petithuguenin-vipr-framework-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 24, 2011) is 4568 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2434' is defined on line 95, but no explicit reference was found in the text == Unused Reference: 'VIPR-PVP' is defined on line 109, but no explicit reference was found in the text == Unused Reference: 'VIPR-RELOAD' is defined on line 115, but no explicit reference was found in the text == Unused Reference: 'VIPR-OVERVIEW' is defined on line 127, but no explicit reference was found in the text == Unused Reference: 'VIPR-VAP' is defined on line 134, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) == Outdated reference: A later version (-26) exists of draft-ietf-p2psip-base-18 == Outdated reference: A later version (-04) exists of draft-petithuguenin-vipr-pvp-01 == Outdated reference: A later version (-04) exists of draft-petithuguenin-vipr-reload-usage-02 -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) == Outdated reference: A later version (-06) exists of draft-jennings-vipr-overview-02 == Outdated reference: A later version (-02) exists of draft-jennings-vipr-vap-01 Summary: 1 error (**), 0 flaws (~~), 12 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 VIPR WG M. Petit-Huguenin 3 Internet-Draft Stonyfish 4 Intended status: Standards Track C. Jennings 5 Expires: April 26, 2012 Cisco 6 J. Rosenberg 7 jdrosen.net 8 October 24, 2011 10 Verification Involving PSTN Reachability (VIPR): Framework 11 draft-petithuguenin-vipr-framework-00 13 Abstract 15 This document describes the framework for Verification Involving PSTN 16 Reachability (VIPR), a set of protocols to automatically and securely 17 provision SIP routes between domains. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. This document may not be modified, 23 and derivative works of it may not be created, except to format it 24 for publication as an RFC or to translate it into languages other 25 than English. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 26, 2012. 39 Copyright Notice 41 Copyright (c) 2011 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 6.1. Normative References . . . . . . . . . . . . . . . . . . . 3 63 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 64 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . . 4 65 Appendix B. Release notes . . . . . . . . . . . . . . . . . . . . 4 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1. Introduction 70 2. Terminology 72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 74 document are to be interpreted as described in [RFC2119]. 76 This document uses some of the terminology defined in [RELOAD] and 77 [RFC3261]. 79 3. Security Considerations 81 4. IANA Considerations 83 5. Acknowledgements 85 This document was written with the xml2rfc tool described in 86 [RFC2629]. 88 6. References 90 6.1. Normative References 92 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 93 Requirement Levels", BCP 14, RFC 2119, March 1997. 95 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 96 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 97 October 1998. 99 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 100 A., Peterson, J., Sparks, R., Handley, M., and E. 101 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 102 June 2002. 104 [RELOAD] Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and 105 H. Schulzrinne, "REsource LOcation And Discovery (RELOAD) 106 Base Protocol", draft-ietf-p2psip-base-18 (work in 107 progress), August 2011. 109 [VIPR-PVP] 110 Rosenberg, J., Jennings, C., and M. Petit-Huguenin, "The 111 Public Switched Telephone Network (PSTN) Validation 112 Protocol (PVP)", draft-petithuguenin-vipr-pvp-01 (work in 113 progress), June 2011. 115 [VIPR-RELOAD] 116 Rosenberg, J., Jennings, C., and M. Petit-Huguenin, "A 117 Usage of Resource Location and Discovery (RELOAD) for 118 Public Switched Telephone Network (PSTN) Verification", 119 draft-petithuguenin-vipr-reload-usage-02 (work in 120 progress), July 2011. 122 6.2. Informative References 124 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 125 June 1999. 127 [VIPR-OVERVIEW] 128 Barnes, M., Jennings, C., Rosenberg, J., and M. Petit- 129 Huguenin, "Verification Involving PSTN Reachability: 130 Requirements and Architecture Overview", 131 draft-jennings-vipr-overview-02 (work in progress), 132 September 2011. 134 [VIPR-VAP] 135 Jennings, C., Rosenberg, J., and M. Petit-Huguenin, 136 "Verification Involving PSTN Reachability: The ViPR Access 137 Protocol (VAP)", draft-jennings-vipr-vap-01 (work in 138 progress), July 2011. 140 Appendix A. Examples 142 Appendix B. Release notes 144 This section must be removed before publication as an RFC. 146 Authors' Addresses 148 Marc Petit-Huguenin 149 Stonyfish 151 Email: marc@stonyfish.com 152 Cullen Jennings 153 Cisco 154 170 West Tasman Drive 155 MS: SJC-21/2 156 San Jose, CA 95134 157 USA 159 Phone: +1 408 421-9990 160 Email: fluffy@cisco.com 162 Jonathan Rosenberg 163 jdrosen.net 164 Monmouth, NJ 165 US 167 Email: jdrosen@jdrosen.net 168 URI: http://www.jdrosen.net