draft-ietf-stir-passport-04.txt   draft-ietf-stir-passport-05.txt 
STIR C. Wendt STIR C. Wendt
Internet-Draft Comcast Internet-Draft Comcast
Intended status: Standards Track J. Peterson Intended status: Standards Track J. Peterson
Expires: January 9, 2017 Neustar Inc. Expires: January 23, 2017 Neustar Inc.
July 8, 2016 July 22, 2016
Persona Assertion Token Persona Assertion Token
draft-ietf-stir-passport-04 draft-ietf-stir-passport-05
Abstract Abstract
This document defines a token format for verifying with non- This document defines a token format for verifying with non-
repudiation the sender of and authorization to send information repudiation the sender of and authorization to send information
related to the originator of personal communications. A related to the originator of personal communications. A
cryptographic signature is defined to protect the integrity of the cryptographic signature is defined to protect the integrity of the
information used to identify the originator of a personal information used to identify the originator of a personal
communications session (e.g. the telephone number or URI) and verify communications session (e.g. the telephone number or URI) and verify
the accuracy of this information at the destination. The the accuracy of this information at the destination. The
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 January 9, 2017. This Internet-Draft will expire on January 23, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 5, line 38 skipping to change at page 5, line 38
The token payload claims should consist of the information which The token payload claims should consist of the information which
needs to be verified at the destination party. This claim should needs to be verified at the destination party. This claim should
correspond to a JWT claim [RFC7519] and be encoded as defined by the correspond to a JWT claim [RFC7519] and be encoded as defined by the
JWS Payload [RFC7515] JWS Payload [RFC7515]
The PASSporT defines the use of a number of standard JWT defined The PASSporT defines the use of a number of standard JWT defined
headers as well as two new custom headers corresponding to the two headers as well as two new custom headers corresponding to the two
parties associated with personal communications, the originator and parties associated with personal communications, the originator and
terminator. These headers or key value pairs are detailed below. terminator. These headers or key value pairs are detailed below.
Key values outside the US-ASCII range should be encoded using percent
encoding as described in section 2.1 of RFC 3986, case normalized as
described in 6.2.2.1 of [RFC3986]. Matching of these values should
use string exact match.
3.2.1. JWT defined claims 3.2.1. JWT defined claims
3.2.1.1. "iat" - Issued at claim 3.2.1.1. "iat" - Issued at claim
The JSON claim MUST include the "iat" [RFC7519] defined claim issued The JSON claim MUST include the "iat" [RFC7519] defined claim issued
at. As defined this should be set to a date cooresponding to the at. As defined this should be set to a date cooresponding to the
origination of the personal communications. The time value should be origination of the personal communications. The time value should be
of the format defined in [RFC7519] Section 2 NumericDate. This is of the format defined in [RFC7519] Section 2 NumericDate. This is
included for securing the token against replay and cut and paste included for securing the token against replay and cut and paste
attacks, as explained further in the security considerations in attacks, as explained further in the security considerations in
skipping to change at page 6, line 24 skipping to change at page 6, line 26
the key represents an identity type and the value is the identity the key represents an identity type and the value is the identity
string. Currently, these identities can be represented as either string. Currently, these identities can be represented as either
telephone numbers or Uniform Resource Indicators (URIs). The telephone numbers or Uniform Resource Indicators (URIs). The
definition of how telephone numbers or URIs and examples are provided definition of how telephone numbers or URIs and examples are provided
below. below.
The "orig" JSON object MUST only have one key value pair representing The "orig" JSON object MUST only have one key value pair representing
the asserted identity of any type (currently either "tn" or "uri") of the asserted identity of any type (currently either "tn" or "uri") of
the originator of the personal communications signaling. the originator of the personal communications signaling.
The "dest" JSON object MUST at least have one key value pair, but The "dest" JSON object MUST have at least have one key value pair,
could have an arbitrary number of destination identities of any type. but could have multiple identity types (i.e. "tn" and/or "uri") but
only one of each. Additionaly, in the case of "dest" only, the
identity type key value MUST be an array signaled by standard JSON
brackets, even when there is a single identity value in the identity
type key value.
3.2.2.1.1. "tn" - Telephone Number identity 3.2.2.1.1. "tn" - Telephone Number identity
If the originating or destination identity is a telephone number, the If the originating or destination identity is a telephone number, the
key representing the identity should be "tn". key representing the identity should be "tn".
Telephone Number strings for "tn" MUST be canonicalized according to Telephone Number strings for "tn" MUST be canonicalized according to
the procedures specified in [I-D.ietf-stir-rfc4474bis] Section 7.2. the procedures specified in [I-D.ietf-stir-rfc4474bis] Section 7.2.
3.2.2.1.2. "uri" - URI identity 3.2.2.1.2. "uri" - URI identity
skipping to change at page 7, line 5 skipping to change at page 7, line 11
We recognize that in the future there may be other standard We recognize that in the future there may be other standard
mechanisms for representing identities. The "orig" and "dest" JSON mechanisms for representing identities. The "orig" and "dest" JSON
objects with "tn" and "uri" allow for other identity types with objects with "tn" and "uri" allow for other identity types with
unique keys to represent these forms. unique keys to represent these forms.
3.2.2.1.4. Examples 3.2.2.1.4. Examples
Single Originator to Single Destination example: Single Originator to Single Destination example:
{ {
"dest":{"uri":["sip:alice@example.com"]},
"iat":"1443208345", "iat":"1443208345",
"orig":{"tn":"12155551212"}, "orig":{"tn":"12155551212"}
"dest":{"uri":"sip:alice@example.com"}
} }
Single Originator to Multiple Destination Identities example: Single Originator to Multiple Destination Identities example:
{ {
"iat":"1443208345",
"orig":{"tn":"12155551212"},
"dest":{ "dest":{
"uri":"sip:alice@example.com", "tn":["12125551212"],
"tn":"12125551212", "uri":["sip:alice@example.com",
"uri":"sip:bob@example.net" "sip:bob@example.net"]
} },
"iat":"1443208345",
"orig":{"tn":"12155551212"}
} }
3.2.2.2. "mky" - Media Key claim 3.2.2.2. "mky" - Media Key claim
Some protocols that use PASSporT convey hashes for media security Some protocols that use PASSporT convey hashes for media security
keys within their signaling in order to bind those keys to the keys within their signaling in order to bind those keys to the
identities established in the signaling layers. One example would be identities established in the signaling layers. One example would be
the DTLS-SRTP key fingerprints carried in SDP via the "a=fingerprint" the DTLS-SRTP key fingerprints carried in SDP via the "a=fingerprint"
attribute; multiple instances of that fingerprint may appear in a attribute; multiple instances of that fingerprint may appear in a
single SDP body corresponding to difference media streams offered. single SDP body corresponding to difference media streams offered.
skipping to change at page 7, line 46 skipping to change at page 8, line 4
whitespace and line feeds must be removed. If there is multiple whitespace and line feeds must be removed. If there is multiple
fingerprint values, more than one, the fingerprint values should be fingerprint values, more than one, the fingerprint values should be
constructed as a JSON array denoted by bracket characters. For the constructed as a JSON array denoted by bracket characters. For the
'dig' key value, the hash value should be the hexadecimal value 'dig' key value, the hash value should be the hexadecimal value
without any colons, in order to provide a more efficient, compact without any colons, in order to provide a more efficient, compact
form to be encoded in PASSporT token claim. form to be encoded in PASSporT token claim.
An example claim with "mky" claim is as follows: An example claim with "mky" claim is as follows:
For an SDP offer that includes the following fingerprint values, For an SDP offer that includes the following fingerprint values,
a=fingerprint:sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65: a=fingerprint:sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:
2E:7D:46:3F:54:42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2 2E:7D:46:3F:54:42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2
a=fingerprint:sha-256 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E: a=fingerprint:sha-256 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:
5D:49:6B:19:E5:7C:AB:3E:4B:65:2E:7D:46:3F:54:42:CD:54:F1 5D:49:6B:19:E5:7C:AB:3E:4B:65:2E:7D:46:3F:54:42:CD:54:F1
the PASSporT Payload object would be: the PASSporT Payload object would be:
{ {
"dest":{"uri":["sip:alice@example.com"]},
"iat":"1443208345", "iat":"1443208345",
"orig":{"tn":"12155551212"}, "mky":[
"dest":{"uri":"sip:alice@example.com"},
"mky":[
{ {
"alg":"sha-256", "alg":"sha-256",
"dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54 "dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54
F17A03A27DF9B07F4619B2" F17A03A27DF9B07F4619B2"
}, },
{ {
"alg":"sha-256", "alg":"sha-256",
"dig":"4AADB9B13F82183B540212DF3E5D496B19E57C "dig":"4AADB9B13F82183B540212DF3E5D496B19E57C
AB3E4B652E7D463F5442CD54F1" AB3E4B652E7D463F5442CD54F1"
} }
] ],
"orig":{"tn":"12155551212"}
} }
3.3. PASSporT Signature 3.3. PASSporT Signature
The signature of the PASSporT is created as specified by JWS using The signature of the PASSporT is created as specified by JWS using
the private key corresponding to the X.509 public key certificate the private key corresponding to the X.509 public key certificate
referenced by the "x5u" header parameter. referenced by the "x5u" header parameter.
4. Extending PASSporT 4. Extending PASSporT
skipping to change at page 9, line 6 skipping to change at page 9, line 9
For the extension of the base set of claims defined in this document, For the extension of the base set of claims defined in this document,
a new JWS header parameter "ppt" MUST be used with a string that a new JWS header parameter "ppt" MUST be used with a string that
uniquely identifies and points to a profile specification that uniquely identifies and points to a profile specification that
defines any new claims that would extend the base set of claims of defines any new claims that would extend the base set of claims of
PASSporT. PASSporT.
An example header with an extended PASSporT profile of "foo" is as An example header with an extended PASSporT profile of "foo" is as
follows: follows:
{ {
"typ":"passport",
"ppt":"foo",
"alg":"ES256", "alg":"ES256",
"ppt":"foo",
"typ":"passport",
"x5u":"https://tel.example.org/passport.cer" "x5u":"https://tel.example.org/passport.cer"
} }
4.2. Extended PASSporT Claims 4.2. Extended PASSporT Claims
Future specifications that define such extensions to the PASSporT Future specifications that define such extensions to the PASSporT
mechanism MUST explicitly designate what claims they include beyond mechanism MUST explicitly designate what claims they include beyond
the base set of claims from this document, the order in which they the base set of claims from this document, the order in which they
will appear, and any further information necessary to implement the will appear, and any further information necessary to implement the
extension. All extensions MUST incorporate the baseline JWT elements extension. All extensions MUST incorporate the baseline JWT elements
skipping to change at page 10, line 10 skipping to change at page 10, line 10
In addition, the JSON header and claim members MUST follow the In addition, the JSON header and claim members MUST follow the
lexicographical ordering and character and string rules defined in lexicographical ordering and character and string rules defined in
[RFC7638] Section 3.3. [RFC7638] Section 3.3.
5.1. Example PASSport deterministic JSON form 5.1. Example PASSport deterministic JSON form
For the example PASSporT Payload shown in Section 3.2.2.2, the For the example PASSporT Payload shown in Section 3.2.2.2, the
following is the deterministic JSON object form. following is the deterministic JSON object form.
{"iat": 1443208345,"orig":{"tn":"12155551212"},"dest": {"dest":{"uri":["sip:alice@example.com"],"iat": 1443208345,"mky"
{"uri":"sip:alice@example.com"},"mky":[{"alg":"sha-256","dig": :[{"alg":"sha-256","dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442
"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54F17A03A27DF9B07F4619 CD54F17A03A27DF9B07F4619B2"},{"alg":"sha-256","dig":"4AADB9B13F8
B2"},{"alg":"sha-256","dig":"4AADB9B13F82183B540212DF3E5D496B19 2183B540212DF3E5D496B19E57CAB3E4B652E7D463F5442CD54F1"}],
E57CAB3E4B652E7D463F5442CD54F1"}]} "orig":{"tn":"12155551212"}}
6. Human Readability 6. Human Readability
JWT [RFC7519] and JWS [RFC7515] are defined to use Base64 and/or UTF8 JWT [RFC7519] and JWS [RFC7515] are defined to use Base64 and/or UTF8
encoding to the Header, Payload, and Signature sections. However, encoding to the Header, Payload, and Signature sections. However,
many personal communications protocols, such as SIP and XMPP, use a many personal communications protocols, such as SIP and XMPP, use a
"human readable" format to allow for ease of use and ease of "human readable" format to allow for ease of use and ease of
operational debugging and monitoring. As such, specifications using operational debugging and monitoring. As such, specifications using
PASSporT may provide guidance on whether Base64 encoding or plain PASSporT may provide guidance on whether Base64 encoding or plain
text will be used for the construction of the PASSporT Header and text will be used for the construction of the PASSporT Header and
skipping to change at page 12, line 16 skipping to change at page 12, line 16
PASSporT defined JWT and JWS. PASSporT defined JWT and JWS.
o Type name: application o Type name: application
o Subtype name: passport o Subtype name: passport
o Required parameters: n/a o Required parameters: n/a
o Optional parameters: n/a o Optional parameters: n/a
o Encoding considerations: 8bit; application/passport values are o Encoding considerations: 8bit; application/passport values outside
encoded as a series of base64url-encoded values (some of which may the US-ASCII range are encoded using percent encoding as described
be the empty string), each separated from the next by a single in section 2.1 of RFC 3986 (some values may be the empty string),
period ('.') character. each separated from the next by a single period ('.') character.
o Security considerations: See the Security Considerations section o Security considerations: See the Security Considerations section
of RFC 7515. of RFC 7515.
o Interoperability considerations: n/a o Interoperability considerations: n/a
o Published specification: draft-ietf-stir-passport-00 o Published specification: draft-ietf-stir-passport-05
o Applications that use this media type: STIR and other applications o Applications that use this media type: STIR and other applications
that require identity related assertion that require identity related assertion
o Fragment identifier considerations: n/a o Fragment identifier considerations: n/a
o Additional information: o Additional information:
* Magic number(s): n/a * Magic number(s): n/a
skipping to change at page 13, line 16 skipping to change at page 13, line 16
8.2.1. Registry Contents Additions Requested 8.2.1. Registry Contents Additions Requested
o Claim Name: "orig" o Claim Name: "orig"
o Claim Description: Originating Identity String o Claim Description: Originating Identity String
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3.2 of draft-ietf-stir- o Specification Document(s): Section 3.2 of draft-ietf-stir-
passport-00 passport-05
o Claim Name: "dest" o Claim Name: "dest"
o Claim Description: Destination Identity String o Claim Description: Destination Identity String
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3.2 of draft-ietf-stir- o Specification Document(s): Section 3.2 of draft-ietf-stir-
passport-00 passport-05
o Claim Name: "mky" o Claim Name: "mky"
o Claim Description: Media Key Fingerprint String o Claim Description: Media Key Fingerprint String
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 3.2 of draft-ietf-stir- o Specification Document(s): Section 3.2 of draft-ietf-stir-
passport-00 passport-05
9. Acknowledgements 9. Acknowledgements
Particular thanks to members of the ATIS and SIP Forum NNI Task Group Particular thanks to members of the ATIS and SIP Forum NNI Task Group
including Jim McEchern, Martin Dolly, Richard Shockey, John Barnhill, including Jim McEchern, Martin Dolly, Richard Shockey, John Barnhill,
Christer Holmberg, Victor Pascual Avila, Mary Barnes, and Eric Burger Christer Holmberg, Victor Pascual Avila, Mary Barnes, Eric Burger for
for their review, ideas, and contributions. Also thanks to Henning their review, ideas, and contributions also thanks to Henning
Schulzrinne, Russ Housley, Alan Johnston, and Richard Barnes for Schulzrinne, Russ Housley, Alan Johnston, Richard Barnes, Mark
valuable feedback on the technical and security aspects of the Miller, and Ted Hardie for valuable feedback on the technical and
document. Additional thanks to Harsha Bellur for assistance in security aspects of the document. Additional thanks to Harsha Bellur
coding the example tokens. for assistance in coding the example tokens.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-stir-rfc4474bis] [I-D.ietf-stir-rfc4474bis]
Peterson, J., Jennings, C., Rescorla, E., and C. Wendt, Peterson, J., Jennings, C., Rescorla, E., and C. Wendt,
"Authenticated Identity Management in the Session "Authenticated Identity Management in the Session
Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-10 Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-10
(work in progress), July 2016. (work in progress), July 2016.
skipping to change at page 15, line 44 skipping to change at page 15, line 44
First, an example PASSporT Protected Header is as follows: First, an example PASSporT Protected Header is as follows:
{ {
"typ":"passport", "typ":"passport",
"alg":"ES256", "alg":"ES256",
"x5u":"https://cert.example.org/passport.cer" "x5u":"https://cert.example.org/passport.cer"
} }
This would be serialized to the form: This would be serialized to the form:
{"typ":"passport","alg":"ES256","x5u":"https://cert.example.org/ {"alg":"ES256","typ":"passport","x5u":"https://cert.example.org/
passport.cer"} passport.cer"}
Encoding this with UTF8 and BASE64 encoding produces this value: Encoding this with UTF8 and BASE64 encoding produces this value:
eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IkVTMjU2IiwieDV1IjoiaHR0cHM6Ly9j eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9 ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9
Second, an example PASSporT Payload is as follows: Second, an example PASSporT Payload is as follows:
{ {
"dest":{"uri":["sip:alice@example.com"]}
"iat":"1443208345", "iat":"1443208345",
"orig":{"tn":"12155551212"}, "orig":{"tn":"12155551212"}
"dest":{"uri":"sip:alice@example.com"}
} }
This would be serialized to the form: This would be serialized to the form:
{"iat":"1443208345","orig":{"tn":"12155551212"},"dest": {"dest":{"uri":["sip:alice@example.com"]},"iat":"1443208345",
{"uri":"sip:alice@example.com"}} "orig":{"tn":"12155551212"}}
Encoding this with the UTF8 and BASE64 encoding produces this value: Encoding this with the UTF8 and BASE64 encoding produces this value:
eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3JpZyI6eyJ0biI6IjEyMTU1NTUxMjEyIn0s eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhd
ImRlc3QiOnsidXJpIjoic2lwOmFsaWNlQGV4YW1wbGUuY29tIn19 CI6IjE0NDMyMDgzNDUiLCJvcmlnIjp7InRuIjoiMTIxNTU1NTEyMTIifX0
Computing the digital signature of the PASSporT Signing Input Computing the digital signature of the PASSporT Signing Input
ASCII(BASE64URL(UTF8(JWS Protected Header)) || '.' || BASE64URL(JWS ASCII(BASE64URL(UTF8(JWS Protected Header)) || '.' || BASE64URL(JWS
Payload)) Payload))
2bbTbLeDIf52Vv0yESUqebUBYrKIuouOfKQME6MD9kfgZ59dMAvvrIC94XsKdzV0 rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYso
3evDS8wd6CubUqSalM7Dpg jNCpTzO3QfPOlckGaS6hEck7w
The final PASSporT token is produced by concatenating the values in The final PASSporT token is produced by concatenating the values in
the order Header.Payload.Signature with period (',') characters. For the order Header.Payload.Signature with period (',') characters. For
the above example values this would produce the following: the above example values this would produce the following:
eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IkVTMjU2IiwieDV1IjoiaHR0cHM6Ly9j eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9 9jZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9
. .
eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3JpZyI6eyJ0biI6IjEyMTU1NTUxMjEyIn0s eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhd
ImRlc3QiOnsidXJpIjoic2lwOmFsaWNlQGV4YW1wbGUuY29tIn19 CI6IjE0NDMyMDgzNDUiLCJvcmlnIjp7InRuIjoiMTIxNTU1NTEyMTIifX0
. .
2bbTbLeDIf52Vv0yESUqebUBYrKIuouOfKQME6MD9kfgZ59dMAvvrIC94XsKdzV0 rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYso
3evDS8wd6CubUqSalM7Dpg jNCpTzO3QfPOlckGaS6hEck7w
A.1. X.509 Private Key Certificate for Example A.1. X.509 Private Key Certificate for Example
-----BEGIN EC PRIVATE KEY----- -----BEGIN EC PRIVATE KEY-----
MHcCAQEEIFeZ1R208QCvcu5GuYyMfG4W7sH4m99/7eHSDLpdYllFoAoGCCqGSM49 MHcCAQEEIFeZ1R208QCvcu5GuYyMfG4W7sH4m99/7eHSDLpdYllFoAoGCCqGSM49
AwEHoUQDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH78YTU8qLS8I5HLHSSmlATLcs AwEHoUQDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH78YTU8qLS8I5HLHSSmlATLcs
lQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g== lQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g==
-----END EC PRIVATE KEY----- -----END EC PRIVATE KEY-----
A.2. X.509 Public Key Certificate for Example A.2. X.509 Public Key Certificate for Example
 End of changes. 32 change blocks. 
65 lines changed or deleted 73 lines changed or added

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