On Dec 9, 2015, at 3:25 PM, Hosnieh Rafiee <i...@rozanak.com> wrote: HR> I would like to suggest the following format (this is the rough version HR> and it is not exact but only giving you an idea that what is the HR> purpose) for a new resource record to store the reference information HR> of bounding of authentication and authorization where authentication HR> can be based on public keys or certificates.
First, read "Domain Name System (DNS) IANA Considerations", RFC 6895. (http://tools.ietf.org/html/rfc6895) That lays out the process of getting a new Resource Record assigned. Second, from the quick description, I don't quite understand what you want to solve. Not complaining, but in preparing to ask for a new type, the use case might need to be clearer. HR> Is DNSOP a right place for that? I asked DANE and they said it HR> is not in their charter. I don't know what you asked the DANE WG. But if it was to add a new DNS RR type, they certainly would not be the best place. DNSOP WG doesn't make decisions on new types (see the RFC for that), but you might get useful advice on this list. HR> If not, please tell me where is the right place. If yes,please HR> tell me what do you think about that and whether or not you HR> support it to draft it. I don't understand it. But don't reuse TXT or HINFO or anything just because it would seem convenient. Consult the RFC for the process. On 12/9/15, 15:29, "DNSOP on behalf of 'Jared Mauch'" <dnsop-boun...@ietf.org on behalf of ja...@puck.nether.net> wrote: JM> You might be able to use HINFO for that as well since it’s JM> designed for two fields already. Jared, You've just made the naughty list for 2015. Santa
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
