draft-ietf-ecrit-phonebcp-11.txt   draft-ietf-ecrit-phonebcp-12.txt 
ecrit B. Rosen ecrit B. Rosen
Internet-Draft NeuStar Internet-Draft NeuStar
Intended status: BCP J. Polk Intended status: BCP J. Polk
Expires: December 6, 2009 Cisco Systems Expires: January 10, 2010 Cisco Systems
June 4, 2009 July 9, 2009
Best Current Practice for Communications Services in support of Best Current Practice for Communications Services in support of
Emergency Calling Emergency Calling
draft-ietf-ecrit-phonebcp-11 draft-ietf-ecrit-phonebcp-12
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with 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 Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 6, 2009. This Internet-Draft will expire on January 10, 2010.
Copyright Notice Copyright Notice
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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 5, line 38 skipping to change at page 5, line 38
SP-2 Proxy servers SHOULD recognize emergency dial strings if for SP-2 Proxy servers SHOULD recognize emergency dial strings if for
some reason the endpoint does not recognize them. This cannot be some reason the endpoint does not recognize them. This cannot be
relied upon by the device if the service provider cannot always relied upon by the device if the service provider cannot always
determine the location of the device. determine the location of the device.
ED-4/SP-3 Emergency calls MUST be marked with a Service URN in the ED-4/SP-3 Emergency calls MUST be marked with a Service URN in the
Request-URI of the INVITE. Request-URI of the INVITE.
ED-5/SP-4 Local dial strings MUST be recognized. ED-5/SP-4 Local dial strings MUST be recognized.
ED-6/SP-5 deleted ED-6/SP-5 Devices MUST be able to be configured with the home country
from which the home dial string(s) can be determined.
ED-7/SP-6 Emergency dial strings SHOULD be determined from LoST ED-7/SP-6 Emergency dial strings SHOULD be determined from LoST
[RFC5222]. Dial Strings MAY be configured directly in the device. [RFC5222]. Dial Strings MAY be configured directly in the device.
AN-1 LoST servers MUST return dial strings for emergency services AN-1 LoST servers MUST return dial strings for emergency services
ED-8 Endpoints which do not recognize emergency dial strings SHOULD ED-8 Endpoints which do not recognize emergency dial strings SHOULD
send dial strings as per [RFC4967]. send dial strings as per [RFC4967].
SP-7 If a proxy server recognizes dial strings on behalf of its SP-7 If a proxy server recognizes dial strings on behalf of its
skipping to change at page 21, line 28 skipping to change at page 21, line 28
Roger Marshall, Stu Goldman, Shida Schubert, James Winterbottom, Roger Marshall, Stu Goldman, Shida Schubert, James Winterbottom,
Barbara Stark, Richard Barnes and Peter Blatherwick. Barbara Stark, Richard Barnes and Peter Blatherwick.
19. References 19. References
19.1. Normative References 19.1. Normative References
[I-D.ietf-geopriv-http-location-delivery] [I-D.ietf-geopriv-http-location-delivery]
Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, Barnes, M., Winterbottom, J., Thomson, M., and B. Stark,
"HTTP Enabled Location Delivery (HELD)", "HTTP Enabled Location Delivery (HELD)",
draft-ietf-geopriv-http-location-delivery-14 (work in draft-ietf-geopriv-http-location-delivery-15 (work in
progress), May 2009. progress), June 2009.
[I-D.ietf-geopriv-lis-discovery] [I-D.ietf-geopriv-lis-discovery]
Thomson, M. and J. Winterbottom, "Discovering the Local Thomson, M. and J. Winterbottom, "Discovering the Local
Location Information Server (LIS)", Location Information Server (LIS)",
draft-ietf-geopriv-lis-discovery-11 (work in progress), draft-ietf-geopriv-lis-discovery-11 (work in progress),
May 2009. May 2009.
[I-D.ietf-mmusic-media-loopback] [I-D.ietf-mmusic-media-loopback]
Venna, N., Jones, P., Roychowdhury, A., and K. Hedayat, Venna, N., Jones, P., Roychowdhury, A., and K. Hedayat,
"An Extension to the Session Description Protocol (SDP) "An Extension to the Session Description Protocol (SDP)
skipping to change at page 22, line 12 skipping to change at page 22, line 12
[I-D.ietf-sip-location-conveyance] [I-D.ietf-sip-location-conveyance]
Polk, J. and B. Rosen, "Location Conveyance for the Polk, J. and B. Rosen, "Location Conveyance for the
Session Initiation Protocol", Session Initiation Protocol",
draft-ietf-sip-location-conveyance-13 (work in progress), draft-ietf-sip-location-conveyance-13 (work in progress),
March 2009. March 2009.
[I-D.ietf-sip-outbound] [I-D.ietf-sip-outbound]
Jennings, C., "Managing Client Initiated Connections in Jennings, C., "Managing Client Initiated Connections in
the Session Initiation Protocol (SIP)", the Session Initiation Protocol (SIP)",
draft-ietf-sip-outbound-19 (work in progress), June 2009. draft-ietf-sip-outbound-20 (work in progress), June 2009.
[LLDP] IEEE, "IEEE802.1ab Station and Media Access Control", [LLDP] IEEE, "IEEE802.1ab Station and Media Access Control",
Dec 2004. Dec 2004.
[LLDP-MED] [LLDP-MED]
TIA, "ANSI/TIA-1057 Link Layer Discovery Protocol - Media TIA, "ANSI/TIA-1057 Link Layer Discovery Protocol - Media
Endpoint Discovery". Endpoint Discovery".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 25, line 47 skipping to change at page 25, line 47
ED-3 Endpoints SHOULD recognize dial strings of emergency calls. If ED-3 Endpoints SHOULD recognize dial strings of emergency calls. If
the service provider always knows the location of the device, then the service provider always knows the location of the device, then
the service provider could recognize them. the service provider could recognize them.
ED-4 Emergency calls MUST be marked with a Service URN in the ED-4 Emergency calls MUST be marked with a Service URN in the
Request-URI of the INVITE. Request-URI of the INVITE.
ED-5 Local dial strings MUST be recognized. ED-5 Local dial strings MUST be recognized.
ED-6 Devices MUST be able to be configured with the home country from
which the home dial string(s) can be determined.
ED-7 Emergency dial strings SHOULD be determined from LoST [RFC5222]. ED-7 Emergency dial strings SHOULD be determined from LoST [RFC5222].
Dial Strings MAY be configured directly in the device. Dial Strings MAY be configured directly in the device.
ED-8 Endpoints which do not recognize emergency dial strings SHOULD ED-8 Endpoints which do not recognize emergency dial strings SHOULD
send dial strings as per [RFC4967]. send dial strings as per [RFC4967].
ED-9 Endpoints SHOULD be able to have home dial strings provisioned ED-9 Endpoints SHOULD be able to have home dial strings provisioned
by configuration. by configuration.
ED-10 Devices SHOULD NOT have one button emergency calling ED-10 Devices SHOULD NOT have one button emergency calling
initiation. initiation.
skipping to change at page 35, line 15 skipping to change at page 35, line 16
SP-2 Proxy servers SHOULD recognize emergency dial strings if for SP-2 Proxy servers SHOULD recognize emergency dial strings if for
some reason the endpoint does not recognize them. This cannot be some reason the endpoint does not recognize them. This cannot be
relied upon by the device if the service provider cannot always relied upon by the device if the service provider cannot always
determine the location of the device. determine the location of the device.
SP-3 Emergency calls MUST be marked with a Service URN in the SP-3 Emergency calls MUST be marked with a Service URN in the
Request-URI of the INVITE. Request-URI of the INVITE.
SP-4 Local dial strings MUST be recognized. SP-4 Local dial strings MUST be recognized.
SP-5 Devices MUST be able to be configured with the home country from
which the home dial string(s) can be determined.
SP-6 Emergency dial strings SHOULD be determined from LoST [RFC5222]. SP-6 Emergency dial strings SHOULD be determined from LoST [RFC5222].
Dial Strings MAY be configured directly in the device. Dial Strings MAY be configured directly in the device.
SP-7 If a proxy server recognizes dial strings on behalf of its SP-7 If a proxy server recognizes dial strings on behalf of its
clients it MUST recognize emergency dial strings represented by clients it MUST recognize emergency dial strings represented by
[RFC4967] and SHOULD recognize emergency dial strings represented by [RFC4967] and SHOULD recognize emergency dial strings represented by
a tel URI [RFC3966]. a tel URI [RFC3966].
SP-8 Service providers MAY provide home dial strings by SP-8 Service providers MAY provide home dial strings by
configuration. configuration.
 End of changes. 9 change blocks. 
8 lines changed or deleted 16 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/