Paul,

   thanks for your comments and support.  We will definitely reference RFC 
draft 1101 in our next version.

- Joe and Dan


On Mar 10, 2012, at 9:28 AM, paul vixie wrote:

> joe, et al,
> 
> your draft-gersch-dnsop-revdns-cidr-01 is very clean and simple; the
> draft and the design are of admirable quality. as a co-author of RFC
> 2317 i agree that it does not suit the needs of bgp security since it
> seeks only to provide a method of fully naming hosts, not networks.
> 
> importantly, i see no reference to RFC 1101 in your draft. RFC 1101
> describes a way to name networks, and while at first it did not seem to
> be compatible with CIDR, implementation (in "netstat -r" back in BSD/OS
> 3.1) showed that RFC 1101 was in fact not as classful as it appeared.
> 
> i recommend a review of these functions, contained in the file dns_nw.c,
> present in bind8 as src/lib/irs/dns_nw.c, and also present in older
> versions of bind9, as well as various versions of netbsd and athena.
> 
> static struct nwent *   get1101byaddr(struct irs_nw *, u_char *, int);
> static struct nwent *   get1101byname(struct irs_nw *, const char *);
> static struct nwent *   get1101answer(struct irs_nw *,
>                                      u_char *ansbuf, int anslen,
>                                      enum by_what by_what,
>                                      int af, const char *name,
>                                      const u_char *addr, int addrlen);
> static struct nwent *   get1101mask(struct irs_nw *this, struct nwent *);
> static int              make1101inaddr(const u_char *, int, char *, int);
> 
> you may find that some of your work has already been done for you, or,
> you may find that this is related work that should be referenced in your
> draft along with the reasons why your proposed method is necessary.
> 
> paul

Joseph Gersch
Chief Operating Officer
Secure64 Software Corporation



_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to