begin process at 2013 05 24 07:14:57
  Trouver un code source :
 
dans
 

RFC écritent par D. Eastlake 3rd

RFC
4635
HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm Identifiers

Use of the domain name system tsig resource record requires specification of a cryptographic message authentication code. currently, identifiers have been specified only for hmac md5 (hashed message authentication code, message digest 5) and gss (...
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Dns, Resource record, Rr, Cryptographic message authentication code, Cmac
RFC
4634
US Secure Hash Algorithms (SHA and HMAC-SHA)

The united states of america has adopted a suite of secure hash algorithms (shas), including four beyond sha-1, as part of a federal information processing standard (fips), specifically sha-224 (rfc 3874), sha-256, sha-384, and sha-512. the purpos...
Déposé par Auteur(s) : D. Eastlake 3rd, T. Hansen
Classé sous : Fips, Federal information processing standard, Sha-224, Sha-256, Sha-384, Sha-512
RFC
4343
Domain Name System (DNS) Case Insensitivity Clarification

Domain name system (dns) names are "case insensitive". this document explains exactly what that means and provides a clear specification of the rules. this clarification updates rfcs 1034, 1035, and 2181. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd
RFC
4305
Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)

The ipsec series of protocols makes use of various cryptographic algorithms in order to provide security services. the encapsulating security payload (esp) and the authentication header (ah) provide two mechanisms for protecting data being sent ov...
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Esp, Ipsec, Authentication, Mechanism, Header, Security, Architecture, Payload, Internet, Protocol, Encapsulating, Ipv4, Ipv6
RFC
4153
XML Voucher: Generic Voucher Language

This document specifies rules for defining voucher properties in xml syntax. a voucher is a logical entity that represents a right to claim goods or services. a voucher can be used to transfer a wide range of electronic values, including coupons, ...
Déposé par Auteur(s) : K. Fujimura, M. Terada, D. Eastlake 3rd
Classé sous : Extensible markup language, Logical entity
RFC
4144
How to Gain Prominence and Influence in Standards Organizations

This document provides simple guidelines that can make it easier for you to gain prominence and influence in most standards organizations. this memo provides information for the internet community.
Déposé par Auteur(s) : D. Eastlake 3rd
RFC
4112
Electronic Commerce Modeling Language (ECML) Version 2 Specification

Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. a standard set of hierarchically-organized payment-related infor...
Déposé par Auteur(s) : D. Eastlake 3rd
RFC
4051
Additional XML Security Uniform Resource Identifiers (URIs)

A number of uniform resource identifiers (uris) intended for use with xml digital signatures, encryption, and canonicalization are defined. these uris identify algorithms and types of keying information. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Digital signatures, Encryption, Canonicalization
RFC
3930
The Protocol versus Document Points of View in Computer Protocols

This document contrasts two points of view: the "document" point of view, where digital objects of interest are like pieces of paper written and viewed by people, and the "protocol" point of view where objects of interest are composite dynamic net...
Déposé par Auteur(s) : D. Eastlake 3rd
RFC
3797
Publicly Verifiable Nominations Committee (NomCom) Random Selection

This document describes a method for making random selections in such a way that the unbiased nature of the choice is publicly verifiable. as an example, the selection of the voting members of the ietf nominations committee (nomcom) from the pool ...
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Internet engineering task force, Ietf
RFC
3741
Exclusive XML Canonicalization, Version 1.0

Canonical xml specifies a standard serialization of xml that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. however, some applications...
Déposé par Auteur(s) : J. Boyer, D. Eastlake 3rd, J. Reagle
Classé sous : Extensible markup language, Namespace
RFC
3675
.sex Considered Dangerous

Periodically there are proposals to mandate the use of a special top level name or an ip address bit to flag "adult" or "unsafe" material or the like. this document explains why this is an ill considered idea from the legal, philosophical, and par...
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Top level domains, Tld, Ip addresses, Internet protocol filters
RFC
3275
(Extensible Markup Language) XML-Signature Syntax and Processing

This document specifies xml (extensible markup language) digital signature processing rules and syntax. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd, J. Reagle, D. Solo
Classé sous : Extensible, Markup, Language
RFC
3174
US Secure Hash Algorithm 1 (SHA1)

The purpose of this document is to make the sha-1 (secure hash algorithm 1) hash algorithm conveniently available to the internet community. this memo provides information for the internet community.
Déposé par Auteur(s) : D. Eastlake 3rd, P. Jones
Classé sous : Fips, Federal, Information, Processing, Standard
RFC
3110
RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)

This document describes how to produce rsa/sha1 sig resource records (rrs) in section 3 and, so as to completely replace rfc 2537, describes how to produce rsa key rrs in section 2. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Rrs, Resource, Records, Security
RFC
3106
ECML v1.1: Field Specifications for E-Commerce

Customers are frequently required to enter substantial amounts of information at an internet merchant site in order to complete a purchase or other transaction, especially the first time they go there. a standard set of information fields is defin...
Déposé par Auteur(s) : D. Eastlake 3rd, T. Goldstein
Classé sous : Electronic, Modeling, Language
RFC
3098
How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$

This memo offers useful suggestions for responsible advertising techniques that can be used via the internet in an environment where the advertiser, recipients, and the internet community can coexist in a productive and mutually respectful fashion...
Déposé par Auteur(s) : T. Gavin, D. Eastlake 3rd, S. Hambridge
Classé sous : Internet, Marketing, Users, Service, Providers, Isps
RFC
3092
Etymology of "Foo"

Approximately 212 rfcs so far, starting with rfc 269, contain the terms `foo', `bar', or `foobar' as metasyntactic variables without any proper explanation or definition. this document rectifies that deficiency. this memo provides information for ...
Déposé par Auteur(s) : D. Eastlake 3rd, C. Manros, E. Raymond
RFC
3075
XML-Signature Syntax and Processing

This document specifies xml (extensible markup language) digital signature processing rules and syntax. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd, J. Reagle, D. Solo
Classé sous : Extensible, Markup, Language
RFC
2936
HTTP MIME Type Handler Detection

Entities composing web pages to provide services over the hypertext transfer protocol (http) frequently have the problem of not knowing what multipurpose internet mail extensions (mime) types have handlers installed at a user's browser. this docum...
Déposé par Auteur(s) : D. Eastlake 3rd, C. Smith, D. Soroka
Classé sous : Multipurpose, Internet, Mail, Extensions, Hypertext, Transfer, Protocol
RFC
2935
Internet Open Trading Protocol (IOTP) HTTP Supplement

The goal of mapping to the transport layer is to ensure that the underlying xml documents are carried successfully between the various parties. this document describes that mapping for the hyper text transport protocol (http), versions 1.0 and 1.1...
Déposé par Auteur(s) : D. Eastlake 3rd, C. Smith
Classé sous : Iotp-http, Hypertext, Xml, Extensible, Markup, Language, Transfer
RFC
2931
DNS Request and Transaction Signatures ( SIG(0)s )

This document describes the minor but non-interoperable changes in request and transaction signature resource records ( sig(0)s ) that implementation experience has deemed necessary. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Domain name system, Data, Security
RFC
2930
Secret Key Establishment for DNS (TKEY RR)

This document describes a transaction key (tkey) rr that can be used in a number of different modes to establish shared secret keys between a dns resolver and server. [standards track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Tkey-rr, Domain name system, Resource record, Transaction key
RFC
2929
Domain Name System (DNS) IANA Considerations

This document discusses the internet assigned number authority (iana) parameter assignment considerations given for the allocation of domain name system (dns) classes, resource record (rr) types, operation codes, error codes, etc. this document sp...
Déposé par Auteur(s) : D. Eastlake 3rd, E. Brunner-Williams, B. Manning
Classé sous : Internet assigned numbers authority, Resource records, Rrs
RFC
2845
Secret Key Transaction Authentication for DNS (TSIG)

This protocol allows for transaction level authentication using shared secrets and one way hashing. it can be used to authenticate dynamic updates as coming from an approved client, or to authenticate responses as coming from an approved recursive...
Déposé par Auteur(s) : P. Vixie, O. Gudmundsson, D. Eastlake 3rd, B. Wellington
Classé sous : Tsig, Domain, Name, System, Transaction, Signature
RFC
2777
Publicly Verifiable Nomcom Random Selection

This document describes a method for making random selections in such a way that the unbiased nature of the choice is publicly verifiable. this memo provides information for the internet community.
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Internet, Engineering, Task force, Ietf
RFC
2706
ECML v1: Field Names for E-Commerce

A standard set of information fields is defined as the first version of an electronic commerce modeling language (ecml) so that this task can be more easily automated, for example by wallet software that could fill in fields. this memo provides in...
Déposé par Auteur(s) : D. Eastlake 3rd, T. Goldstein
Classé sous : Electronic, Commerce, Modeling, Language, Merchant, Site. web
RFC
2606
Reserved Top Level DNS Names

To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. in addition, a few second level domain names reserved for use as examples are doc...
Déposé par Auteur(s) : D. Eastlake 3rd, A. Panitz
Classé sous : Domain, Name, System, Private
RFC
2541
DNS Security Operational Considerations

This document discusses these operational aspects for keys and signatures used in connection with the key and sig dns resource records. this memo provides information for the internet community.
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Dns-soc, Domain, Name, System, Cryptology, Resource, Records, Rrs
RFC
2540
Detached Domain Name System (DNS) Information

A standard format is defined for representing detached dns information. this is anticipated to be of use for storing information retrieved from the domain name system (dns), including security information, in archival contexts or contexts not conn...
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Dns-info, Security, Digital, Signatures, Authentication
RFC
2539
Storage of Diffie-Hellman Keys in the Domain Name System (DNS)

A standard method for storing diffie-hellman keys in the domain name system is described which utilizes dns key resource records. [standards-track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Dhk-dns, Cryptology, Authentication, Security, Signatures, Digital
RFC
2538
Storing Certificates in the Domain Name System (DNS)

Cryptographic public key are frequently published and their authenticity demonstrated by certificates. a cert resource record (rr) is defined so that such certificates and related certificate revocation lists can be stored in the domain name syste...
Déposé par Auteur(s) : D. Eastlake 3rd, O. Gudmundsson
Classé sous : Sc-dns, Cryptology, Authenticity
RFC
2537
RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)

A standard method for storing rsa keys and and rsa/md5 based signatures in the domain name system is described which utilizes dns key and sig resource records. [standards-track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Message, Digest, Signatures, Cryptology, Security
RFC
2536
DSA KEYs and SIGs in the Domain Name System (DNS)

A standard method for storing us government digital signature algorithm keys and signatures in the domain name system is described which utilizes dns key and sig resource records. [standards-track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Digital, Signature, Algorithm, Signatures, Cryptology
RFC
2535
Domain Name System Security Extensions

This document incorporates feedback on rfc 2065 from early implementers and potential users. [standards-track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Dns-secext, Dns, Authentication
RFC
2137
Secure Domain Name System Dynamic Update

This memo describes how to use dnssec digital signatures covering requests and data to secure updates and restrict updates to those authorized to perform them as indicated by the updater's possession of cryptographic keys. [standards-track]
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Sdnsdu, Dns, Digital, Signatures, Cryptographic
RFC
2065
Domain Name System Security Extensions

The domain name system (dns) has become a critical operational part of the internet infrastructure yet it has no strong security mechanisms to assure data integrity or authentication. extensions to the dns are described that provide these services...
Déposé par Auteur(s) : D. Eastlake 3rd, C. Kaufman
Classé sous : Dns-sec, Dns, Authentication, Encryption
RFC
1898
CyberCash Credit Card Protocol Version 0.8

This document covers only the current cybercash system which is one of the few operational systems in the rapidly evolving area of internet payments. this memo provides information for the internet community. this memo does not specify an internet...
Déposé par Auteur(s) : D. Eastlake 3rd, B. Boesch, S. Crocker, M. Yesil
Classé sous : General, Payments, System
RFC
1750
Randomness Recommendations for Security

Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. this paper points out many pitfalls in using traditional pseudo-random number generation techniques for choosing such quantities. it recommends the...
Déposé par Auteur(s) : D. Eastlake 3rd, S. Crocker, J. Schiller
Classé sous : Random, Numbers, Seed
RFC
1455
Physical Link Security Type of Service

This rfc documents an experimental protocol providing a type of service (tos) to request maximum physical link security. this is an addition to the types of service enumerated in rfc 1349: type of service in the internet protocol suite. this memo ...
Déposé par Auteur(s) : D. Eastlake 3rd
Classé sous : Tos-ls, Tos


Nos sponsors


Sondage...

Comparez les prix

CalendriCode

Mai 2013
LMMJVSD
  12345
6789101112
13141516171819
20212223242526
2728293031  

Consulter la suite du CalendriCode

Photothèque

A découvrir



 
Développement réalisé par Nicolas SOREL (Nix) avec l'aide de : Cyril DURAND et Emmanuel (EBArtSoft), Merci à Vincent pour ses précieux conseils.
CodeS-SourceS.com© Toute reproduction même partielle est interdite sauf accord écrit du Webmaster
CodeS-SourceS.com© est une marque déposée tous droits réservés

Google Coop CodeS-SourceS Google Coop CodeS-SourceS
Temps d'éxécution de la page : 0,078 sec (3)

Nous contacter | Annoncer sur CodeS-SourceS | Mentions légales