A. Submission Date:2002/04/05 B.1 Submission Type: [X] New RRTYPE [ ] Modification to RRTYPE B.2 Kind of RR: [X] Data RR [ ] Meta-RR C. Contact Information for submitter : Name: Eugene Adell Email Address: eugene.adell@gmail.com International telephone number: +33699056914 Other contact handles: D. Motivation for the new RRTYPE application. Introduce a couple of RR types working together in order to better secure remote access to partner applications E. Description of the proposed RR type. CRC contains a limited list of authorized networks for a particular application F. What existing RRTYPE or RRTYPEs come closest to filling that need and why are they unsatisfactory? TXT RRTYPE allows the storage of any text data but in practice is usually associated with more or less fixed name or data which is not what is needed here. A dedicated RRTYPE is easier to identify and manage by a security team other than the usual DNS operator team. G. What mnemonic is requested for the new RRTYPE (optional)? CRC H. Does the requested RRTYPE make use of any existing IANA registry or require the creation of a new IANA subregistry in DNS Parameters? It uses the existing Resource Record (RR) TYPEs registry I. Does the proposal require/expect any changes in DNS servers/resolvers that prevent the new type from being processed as an unknown RRTYPE (see [RFC3597])? No J. Comments: None A. Submission Date:2002/04/05 B.1 Submission Type: [X] New RRTYPE [ ] Modification to RRTYPE B.2 Kind of RR: [X] Data RR [ ] Meta-RR C. Contact Information for submitter : Name: Eugene Adell Email Address: eugene.adell@gmail.com International telephone number: +33699056914 Other contact handles: D. Motivation for the new RRTYPE application. Introduce a couple of RR types working together in order to better secure remote access to partner applications E. Description of the proposed RR type. CRS contains a requirement value and a list of ports indicating what kind of authorization check is done during the application authentication process F. What existing RRTYPE or RRTYPEs come closest to filling that need and why are they unsatisfactory? TXT RRTYPE allows the storage of any text data but in practice is usually associated with more or less fixed name or data which is not what is needed here. A dedicated RRTYPE is easier to identify and manage by a security team other than the usual DNS operator team. G. What mnemonic is requested for the new RRTYPE (optional)? CRS H. Does the requested RRTYPE make use of any existing IANA registry or require the creation of a new IANA subregistry in DNS Parameters? It uses the existing Resource Record (RR) TYPEs registry I. Does the proposal require/expect any changes in DNS servers/resolvers that prevent the new type from being processed as an unknown RRTYPE (see [RFC3597])? No J. Comments: None