The document candidly categorizes itself, in Section 1, as “a pedantic network
protocol description”. As such, I think it might be appropriate for it to
describe DNS names as appearing in the only form that is unambiguous and
implementation-agnostic, i.e. dot-terminated FQDN.
Having said
1.
##which they are generated. The Key Tag is a 16-bit value computed
##from the RDATA portion of a DNSKEY RR using a formula similar to a
##ones-complement checksum. RRSIG RRs contain a Key Tag field whose
Suggest a reference to the section where the formula is defined, lest the
On Mon, Apr 2, 2018 at 6:26 AM, Mukund Sivaraman wrote:
> On Mon, Apr 02, 2018 at 03:20:02AM -0700, internet-dra...@ietf.org wrote:
> >
> > A new version of I-D, draft-muks-dnsop-dns-squash-01.txt
> > has been successfully submitted by Mukund Sivaraman and posted to the
> > IETF
At Fri, 6 Apr 2018 04:35:44 +,
Evan Hunt wrote:
> > At Thu, 5 Apr 2018 13:46:29 -0400,
> > tjw ietf wrote:
> >
> > > What is work: An "informational" document being used as standard is people
> > > taking a submitted (expired) draft as "standard"?
> >
> >
On Mon, Apr 9, 2018 at 11:18 AM Suzanne Woolf
wrote:
> Warren,
>
> Thanks for clarifying this for the WG.
No worries - and just to remind the WG: I will never be the Responsible AD
for a document for which I am an author, and will always recuse myself
during eval, etc.
On Sat, Apr 7, 2018 at 5:41 AM, Benno Overeinder wrote:
> Hi Suzanne, Warren, DNSOP WG,
>
> > On 7 Apr 2018, at 04:09, Warren Kumari wrote:
> >
> > On Fri, Apr 6, 2018 at 5:49 PM, Suzanne Woolf
> wrote:
> >>
> >>
> >> WG
Warren,
Thanks for clarifying this for the WG.
For those who don’t like to worry about process, just note that Warren has done
the right thing to head off any potential process issue with having the same
person acting as both an editor of the document and the Area Director
responsible for
Hello all,
Obviously I cannot (nor would I want to) be the responsible AD for
this document, and so I asked for volunteers - Terry Manderson (CCed)
has kindly volunteered to carry the torch on this document.
Thanks Terry!
W
--
I don't think the execution is relevant when it was obviously a bad
On Mon, Apr 2, 2018 at 8:12 PM, Matthew Pounsett wrote:
>
>
> On 2 April 2018 at 09:56, Warren Kumari wrote:
>>
>>
>> This is not clearly a modification to the intended consensus (yet),
>> and currently feels unclear to me, so I'm going to give this another
> On 8 Apr 2018, at 19:14, John R. Levine wrote:
>
> I know it's ugly, but is there any rule that forbids putting an MX in a
> reverse zone?
No, though talk to Joe Abley if you want some practical interop experience :-)
On 8.4.2018 20:14, John R. Levine wrote:
> One day when I should have been doing something else, I make some .arpa
> e-mail addresses.
>
> Try sending mail to jo...@m.183.57.64.in-addr.arpa and in all likelihood
> I will get it.
>
> I know it's ugly, but is there any rule that forbids putting
11 matches
Mail list logo