Spencer Dawkins has entered the following ballot position for
draft-ietf-dnsop-resolver-priming-09: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
On 30 Nov 2016, at 14:49, John Levine wrote:
In article you
write:
On Wed, 30 Nov 2016, Matt Larson wrote:
Did you see my message earlier in the thread? Is there a reason you
don't include a third option: retrieving the trust anchor file
published
by IANA/PTI (https://data.iana.org/root-an
In article you write:
>On Wed, 30 Nov 2016, Matt Larson wrote:
>
>> Did you see my message earlier in the thread? Is there a reason you
>> don't include a third option: retrieving the trust anchor file published
>> by IANA/PTI (https://data.iana.org/root-anchors/root-anchors.xml) and
>> valida
Terry Manderson has entered the following ballot position for
draft-ietf-dnsop-resolver-priming-09: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
On Wed, Nov 30, 2016 at 10:43 AM, Matt Larson wrote:
>
> > On Nov 29, 2016, at 8:31 AM, Olafur Gudmundsson wrote:
> >
> > IMHO the device should have two sources of truth for DNSSEC root TA
> > a) DNS via RFC5011
> > b) Secure Software update from the vendor
> >
> > If both fail then operator sh
On 30 Nov 2016, at 8:00, Mikael Abrahamsson wrote:
On Wed, 30 Nov 2016, Matt Larson wrote:
Did you see my message earlier in the thread? Is there a reason you
don't include a third option: retrieving the trust anchor file
published by IANA/PTI
(https://data.iana.org/root-anchors/root-anchor
Matt Larson wrote:
>
> Is there a reason you don't include a third option: retrieving the trust
> anchor file published by IANA/PTI
> (https://data.iana.org/root-anchors/root-anchors.xml) and validating
> with the detached S/MIME signature published in the same place
> (https://data.iana.org/root-
All
The Call for Adoption has ended with expected results, and the draft has
been adopted. Thanks to everyone for comments, both in the meeting in Seoul
and on the list. Now the real work begins.
Authors, if you be so kind as toupload the new version with the appropriate
nomenclature,
thanks
ti
On Wed, 30 Nov 2016, Matt Larson wrote:
Did you see my message earlier in the thread? Is there a reason you
don't include a third option: retrieving the trust anchor file published
by IANA/PTI (https://data.iana.org/root-anchors/root-anchors.xml) and
validating with the detached S/MIME signat
> On Nov 29, 2016, at 8:31 AM, Olafur Gudmundsson wrote:
>
> IMHO the device should have two sources of truth for DNSSEC root TA
> a) DNS via RFC5011
> b) Secure Software update from the vendor
>
> If both fail then operator should be invoked.
Did you see my message earlier in the thread?
Stephen Farrell has entered the following ballot position for
draft-ietf-dnsop-resolver-priming-09: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
11 matches
Mail list logo
