|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-1 uses XML-Signature Syntax and Processing Facilities as discussed in [17] for security.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3075
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
ABA Digital Signature Guidelines./
http://www.abanet.org/scitech/ec/isc/dsgfree.html/
/
Bourret Declaring Elements and Attributes in an XML DTD./
Ron Bourret. http://www.informatik.tu-/
darmstadt.de/DVS1/staff/bourret/xml/xmldtd.html/
/
DOM Document Object Model (DOM) Level 1 Specification./
W3C Recommendation. V. Apparao, S. Byrne, M./
Champion, S. Isaacs, I. Jacobs, A. Le Hors, G./
Nicol, J. Robie, R. Sutor, C. Wilson, L. Wood./
October 1998. http://www.w3.org/TR/1998/REC-DOM-/
Level-1-19981001//
DSS FIPS PUB 186-1. Digital Signature Standard (DSS)./
U.S. Department of Commerce/National Institute of/
Standards and Technology./
http://csrc.nist.gov/fips/fips1861.pdf/
/
HMAC Krawczyk, H., Bellare, M. and R. Canetti, "HMAC:/
Keyed-Hashing for Message Authentication", RFC/
2104, February 1997./
http://www.ietf.org/rfc/rfc2104.txt/
/
HTTP Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,/
Masinter, L., Leach, P. and T. Berners-Lee,/
"Hypertext Transfer Protocol -- HTTP/1.1", RFC/
2616, June 1999./
http://www.ietf.org/rfc/rfc2616.txt/
/
KEYWORDS Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
http://www.ietf.org/rfc/rfc2119.txt/
/
LDAP-DN Wahl, M., Kille, S. and T. Howes, "Lightweight/
Directory Access Protocol (v3): UTF-8 String/
Representation of Distinguished Names", RFC 2253,/
December 1997. http://www.ietf.org/rfc/rfc2253.txt/
/
MD5 Rivest, R., "The MD5 Message-Digest Algorithm", RFC/
1321, April 1992./
http://www.ietf.org/rfc/rfc1321.txt/
/
MIME Freed, N. and N. Borenstein, "Multipurpose Internet/
Mail Extensions (MIME) Part One: Format of Internet/
Message Bodies", RFC 2045, November 1996./
http://www.ietf.org/rfc/rfc2045.txt/
/
NFC TR15. Unicode Normalization Forms. M. Davis, M./
Drst. Revision 18: November 1999./
/
PGP Callas, J., Donnerhacke, L., Finney, H. and R./
Thayer, "OpenPGP Message Format", November 1998./
http://www.ietf.org/rfc/rfc2440.txt/
/
RANDOM Eastlake, D., Crocker, S. and J. Schiller,/
"Randomness Recommendations for Security", RFC/
1750, December 1994./
http://www.ietf.org/rfc/rfc1750.txt/
RDF RDF Schema W3C Candidate Recommendation. D./
Brickley, R.V. Guha. March 2000./
http://www.w3.org/TR/2000/CR-rdf-schema-20000327//
RDF Model and Syntax W3C Recommendation. O./
Lassila, R. Swick. February 1999./
http://www.w3.org/TR/1999/REC-rdf-syntax-19990222//
/
1363 IEEE 1363: Standard Specifications for Public Key/
Cryptography. August 2000./
/
PKCS1 Kaliski, B. and J. Staddon, "PKCS #1: RSA/
Cryptography Specifications Version 2.0", RFC 2437,/
October 1998. http://www.ietf.org/rfc/rfc2437.txt/
/
SAX SAX: The Simple API for XML David Megginson et. al./
May 1998. http://www.megginson.com/SAX/index.html/
/
SHA-1 FIPS PUB 180-1. Secure Hash Standard. U.S./
Department of Commerce/National Institute of/
Standards and Technology./
http://csrc.nist.gov/fips/fip180-1.pdf/
/
Unicode The Unicode Consortium. The Unicode Standard./
http://www.unicode.org/unicode/standard/standard.html/
/
UTF-16 Hoffman, P. and F. Yergeau, "UTF-16, an encoding of/
ISO 10646", RFC 2781, February 2000./
http://www.ietf.org/rfc/rfc2781.txt/
/
UTF-8 Yergeau, F., "UTF-8, a transformation format of ISO/
10646", RFC 2279, January 1998./
http://www.ietf.org/rfc/rfc2279.txt/
/
URI Berners-Lee, T., Fielding, R. and L. Masinter,/
"Uniform Resource Identifiers (URI): Generic/
Syntax", RFC 2396, August 1998./
http://www.ietf.org/rfc/rfc2396.txt/
/
URI-Literal Hinden, R., Carpenter, B. and L. Masinter, "Format/
for Literal IPv6 Addresses in URL's", RFC 2732,/
December 1999. http://www.ietf.org/rfc/rfc2732.txt/
/
URL Berners-Lee, T., Masinter, L. and M. McCahill,/
"Uniform Resource Locators (URL)", RFC 1738,/
December 1994. http://www.ietf.org/rfc/rfc1738.txt/
URN Moats, R., "URN Syntax" RFC 2141, May 1997./
http://www.ietf.org/rfc/rfc2141.txt/
/
Daigle, L., van Gulik, D., Iannella, R. and P./
Faltstrom, "URN Namespace Definition Mechanisms",/
RFC 2611, June 1999./
http://www.ietf.org/rfc/rfc2611.txt/
/
X509v3 ITU-T Recommendation X.509 version 3 (1997)./
"Information Technology - Open Systems/
Interconnection - The Directory Authentication/
Framework" ISO/IEC 9594-8:1997./
/
XHTML 1.0 XHTML(tm) 1.0: The Extensible Hypertext Markup/
Language Recommendation. S. Pemberton, D. Raggett,/
et. al. January 2000./
http://www.w3.org/TR/2000/REC-xhtml1-20000126//
/
XLink XML Linking Language. Working Draft. S. DeRose, D./
Orchard, B. Trafford. July 1999./
http://www.w3.org/1999/07/WD-xlink-19990726/
/
XML Extensible Markup Language (XML) 1.0/
Recommendation. T. Bray, J. Paoli, C. M. Sperberg-/
McQueen. February 1998./
http://www.w3.org/TR/1998/REC-xml-19980210/
/
XML-C14N J. Boyer, "Canonical XML Version 1.0", RFC 3076,/
September 2000. http://www.w3.org/TR/2000/CR-xml-/
c14n-20001026/
http://www.ietf.org/rfc/rfc3076.txt/
/
XML-Japanese XML Japanese Profile. W3C NOTE. M. MURATA April/
2000 http://www.w3.org/TR/2000/NOTE-japanese-xml-/
20000414//
/
XML-MT Whitehead, E. and M. Murata, "XML Media Types",/
July 1998. http://www.ietf.org/rfc/rfc2376.txt/
/
XML-ns Namespaces in XML Recommendation. T. Bray, D./
Hollander, A. Layman. Janury 1999./
http://www.w3.org/TR/1999/REC-xml-names-19990114/
/
XML-schema XML Schema Part 1: Structures Working Draft. D./
Beech, M. Maloney, N. Mendelshohn. September 2000./
http://www.w3.org/TR/2000/WD-xmlschema-1-20000922//
XML Schema Part 2: Datatypes Working Draft. P./
Biron, A. Malhotra. September 2000./
http://www.w3.org/TR/2000/WD-xmlschema-2-20000922//
/
XML-Signature-RD Reagle, J., "XML Signature Requirements", RFC 2907,/
April 2000. http://www.w3.org/TR/1999/WD-xmldsig-/
requirements-19991014/
http://www.ietf.org/rfc/rfc2807.txt/
/
XPath XML Path Language (XPath)Version 1.0./
Recommendation. J. Clark, S. DeRose. October 1999./
http://www.w3.org/TR/1999/REC-xpath-19991116/
/
XPointer XML Pointer Language (XPointer). Candidate/
Recommendation. S. DeRose, R. Daniel, E. Maler./
http://www.w3.org/TR/2000/CR-xptr-20000607/
/
XSL Extensible Stylesheet Language (XSL) Working Draft./
S. Adler, A. Berglund, J. Caruso, S. Deach, P./
Grosso, E. Gutentag, A. Milowski, S. Parnell, J./
Richman, S. Zilles. March 2000./
http://www.w3.org/TR/2000/WD-xsl-/
20000327/xslspec.html/
/
XSLT XSL Transforms (XSLT) Version 1.0. Recommendation./
J. Clark. November 1999./
http://www.w3.org/TR/1999/REC-xslt-19991116.html/
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
