128 being one of the supported algorithms,
but one of the SHA-2 algorithms should be selected for MUST implement.
--
Robert Story <http://www.isi.edu/~rstory>
USC Information Sciences Institute <http://www.isi.edu/>
___
DNSOP mailing list
D
ed a SNMP over DNS draft? :-p
--
Robert Story <http://www.isi.edu/~rstory>
USC Information Sciences Institute <http://www.isi.edu/>
pgpdf4eOn2zwe.pgp
Description: OpenPGP digital signature
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf
actors here (resolver
> implementers, zone managers) so that it was more clear who was doing
> what.
I agree that the draft should be clearer on who needs to do what.
--
Robert Story <http://www.isi.edu/~rstory>
USC Information Sciences Institute <http://www.isi.edu/>
t;
> and an A record response for the invalid name.
Similarly, shouldn't all three of these be "an A or AAAA record"?
The table following this text also only specifies "A" for responses.
--
Robert Story <http://www.isi.edu/~rstory>
of static
configuration, or learned via 5011.
--
Robert Story <http://www.isi.edu/~rstory>
USC Information Sciences Institute <http://www.isi.edu/>
pgpwVyffI5pQ4.pgp
Description: OpenPGP digital signature
___
DNSOP mailing list
DNSOP@ie
is that there's no need to start the
flame-fest/endless arguments until it looks like there is actually some
support for the idea.
--
Robert Story
SPARTA
signature.asc
Description: PGP signature
___
DNSOP mailing list
DNSOP@ietf.org
https://www1.ietf.org
, but the process is
supposed to be open. 3979 even explicitly acknowledges that IPR
claims can be in some cases be disingenuous, i.e., made to affect the
IETF Standards Process rather than to inform.
--
Robert Story
SPARTA
signature.asc
Description: PGP signature
about whether or not to provide
reverse DNS.
[1] http://www.postmaster.aol.com/guidelines/standards.html
[2]
http://www.spamhaus.org/faq/answers.lasso?section=ISP%20Spam%20Issues#128
--
Robert Story
SPARTA
signature.asc
Description: PGP signature
