On 10/10/18 9:33 PM, Dave Crocker wrote:
The datatracker entries are:
DNS Scoped Data Through "Underscore" Naming of Attribute Leaves
https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf/
Just to make sure you catch them in your audit, the following entries
are still missin
Folks,
Based on the latest round of comments, I've submitted revised versions
of the two drafts, mostly so that their diffs would be easily obtained.
I didn't do the careful, fine-grained review and audit of the changes
that will be needed, since I-D numbers are cheap and I figured
convenien
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.
Title : DNS Attrleaf Changes: Fixing Specifications with
Underscored Node Name Use
Author : Dave Croc
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.
Title : DNS Scoped Data Through "Underscore" Naming of
Attribute Leaves
Author : Dave Crocker
Ben Campbell has entered the following ballot position for
draft-ietf-dnsop-attrleaf-13: 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 refer to ht
Spencer Dawkins has entered the following ballot position for
draft-ietf-dnsop-attrleaf-fix-04: 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 refe
Hi, Dave,
On Wed, Oct 10, 2018 at 3:52 PM Dave Crocker wrote:
> On 10/10/2018 4:38 PM, Paul Vixie wrote:
> > i can live with that.
> >
> >>
> >> which is one heck of a lot of "resource record types" in the same, short
> >> paragraph.
> >
> > truth hurts.
>
> mumble. drat. that's two in favor, wh
Spencer Dawkins has entered the following ballot position for
draft-ietf-dnsop-attrleaf-fix-04: Discuss
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 refer to
On 10/10/2018 2:09 PM, Benjamin Kaduk wrote:
One other comment, in Section 3.1:
Why is the new text only placing a "SHOULD be registered" requirement, as
opposed to MUST?
It permits use-before-registration, which avoids registration as a
barrier to adoption.
There is essentially no real r
On 10/10/2018 4:38 PM, Paul Vixie wrote:
i can live with that.
which is one heck of a lot of "resource record types" in the same, short
paragraph.
truth hurts.
mumble. drat. that's two in favor, which for this topic rates as
overwhelming consensus.
sigh. k. if you insist...
Dave Crocker wrote:
which I believe is fully clear, given that there does not appear to me
to be any candidate for intepreting 'one' other than 'resource record
type', but worse, making the change you suggest would produce:
DNS data semantics have been limited to the specification of par
On 10/10/2018 3:40 PM, Spencer Dawkins wrote:
Spencer Dawkins has entered the following ballot position for
draft-ietf-dnsop-attrleaf-13: 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
int
On Wed, Oct 10, 2018 at 1:18 PM Dave Crocker wrote:
> Eric,
>
> On 10/9/2018 7:23 PM, Eric Rescorla wrote:
> >> However some services have defined an operational convention,
> which
> >> applies to DNS leaf nodes that are under a DNS branch having one
> or
> >> more reserved nod
Eric,
On 10/9/2018 7:23 PM, Eric Rescorla wrote:
However some services have defined an operational convention, which
applies to DNS leaf nodes that are under a DNS branch having one or
more reserved node names, each beginning with an _underscore. The
underscored naming c
On Wed, Oct 10, 2018 at 5:15 AM "Mirja Kühlewind (IETF)" <
i...@kuehlewind.net> wrote:
> Hi Warren, hi Ted,
>
> sorry I was on holidays a couple of days last week and am completely
> behind everything. Will try to have a look as soon as possible. Maybe
> Friday or next week…
>
Ok, thank you.
Not
Spencer Dawkins has entered the following ballot position for
draft-ietf-dnsop-attrleaf-13: 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 refer to
Alissa,
On 10/10/2018 2:48 PM, Alissa Cooper wrote:
On Oct 10, 2018, at 2:32 PM, Dave Crocker wrote:
On 10/10/2018 10:52 AM, Alissa Cooper wrote:
I think this document needs to state explicitly which updates apply to which
existing RFCs. That is, I would expect to see in sections 2.1, 2.2, an
Hi Dave,
> On Oct 10, 2018, at 2:32 PM, Dave Crocker wrote:
>
> On 10/10/2018 10:52 AM, Alissa Cooper wrote:
>> I think this document needs to state explicitly which updates apply to which
>> existing RFCs. That is, I would expect to see in sections 2.1, 2.2, and 2.3
>> the list of which docume
On 10/10/2018 10:52 AM, Alissa Cooper wrote:
I think this document needs to state explicitly which updates apply to which
existing RFCs. That is, I would expect to see in sections 2.1, 2.2, and 2.3
the list of which documents are updated by each section. I realize this can be
intuited, but typic
Benjamin Kaduk has entered the following ballot position for
draft-ietf-dnsop-attrleaf-fix-04: 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 refer
Benjamin Kaduk has entered the following ballot position for
draft-ietf-dnsop-attrleaf-13: 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 refer to
On 10/10/2018 12:54 PM, Alissa Cooper wrote:
The Gen-ART review for attrleaf is
athttps://mailarchive.ietf.org/arch/msg/dnsop/dq-cwawY1UqoGJWFUxQPuWv0oPc.
hmmm. I see that its addressing should have reached me but I'm not
finding a copy in my mail archive. Thanks for the pointer:
From: E
Hi Dave,
> On Oct 10, 2018, at 12:49 PM, Dave Crocker wrote:
>
> On 10/10/2018 10:03 AM, Alissa Cooper wrote:
>> I agree with Alexey. It seems like the expert is being asked to do the review
>> that IANA would typically do itself.
>
> Point taken. However, there was wg discussion about the cho
On 10/10/2018 10:03 AM, Alissa Cooper wrote:
I agree with Alexey. It seems like the expert is being asked to do the review
that IANA would typically do itself.
Point taken. However, there was wg discussion about the choice and it
landed on this.
I'll await either wg or iesg direction for sp
On 10/10/2018 11:52 AM, Adam Roach wrote:
I think this reply covers everything that warranted a specific response
except for the questions in the following three comments, which are
asking specifically about URI RRs:
Drat. Sorry. I'll blame it on limited screen real estate while
traveling,
On 10/10/18 8:51 AM, Dave Crocker wrote:
Responding to your additional comments...
Thanks!
I think this reply covers everything that warranted a specific response
except for the questions in the following three comments, which are
asking specifically about URI RRs:
Comment 1: Was the rem
On 10/10/18 8:51 AM, Dave Crocker wrote:
If I am reading 6763 correctly, in terms of 'global' underscored use
and distinguishing its 'hypotheticals' from actual usage, it only
reserves _tcp and _udp. (For example, its use of _ipp is second-level
and therefore not global.)
That's my reading
Francesa, thanks for your review. Dave, thanks for your responses. I entered a
DISCUSS ballot based on the issue raised about unused citations.
Typically the abstract does contain an explanation of the document(s) being
updated. In this case the list is so long that I’m not sure it’s worth it.
Alissa Cooper has entered the following ballot position for
draft-ietf-dnsop-attrleaf-fix-04: Discuss
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 refer to ht
Erik, thanks for your review. I have entered a No Objection ballot.
Alissa
> On Sep 26, 2018, at 3:57 PM, Erik Kline
> wrote:
>
> Reviewer: Erik Kline
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all I
Alissa Cooper has entered the following ballot position for
draft-ietf-dnsop-attrleaf-13: 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 refer to h
Responding to your additional comments...
On 10/8/2018 11:43 PM, Adam Roach wrote:
Echoing comments from my review of draft-ietf-dnsop-attrleaf: I believe this
document needs to also include RFC 6763 and RFC 4386; and that it should not
include RFC 6733. Please see that review for details.
R
On 10/10/2018 8:43 AM, "Mirja Kühlewind (IETF)" wrote:
However re-consider the appropriate intended status for this doc!
I assume that is still something that the IESG resolves, independent of
whatever is on the draft.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
__
Hi Dave,
no I didn’t see that mail (quite a bit behind mail at the moment) but looked it
up now. I have to say the argument of have a clean registry doc is not that
convincing for me but it this fine. However re-consider the appropriate
intended status for this doc!
Mirja
> Am 10.10.2018 um
On 10/10/2018 7:26 AM, Mirja Kühlewind wrote:
I don't quite understand why it was seen as beneficial by the group that this
doc has been split up,
Did you see the note I posted yesterday about this (in the context of
having the base refer to the -fix, but including an explanation for the
spl
On 10/9/2018 3:33 PM, Adam Roach wrote:
That's a fair point. I still believe that this arrangement makes the
situation as it pertains to URL RRs worse rather than better, but I'm
willing to call myself in the rough here. If another AD sees fit to
DISCUSS this issue, I will support them. But I'l
Mirja Kühlewind has entered the following ballot position for
draft-ietf-dnsop-attrleaf-fix-04: 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 refe
Hi all,
Recently I'm engaged in a project on the issue of IPv6 GeoIP for a large
Internet company. IPv6 GeoIP is identified as an notable chanllge to
mitigate their Geolocation-based application to IPv6. I come up with a idea
to summarize the existing practice and propsed technologies into a
infor
Hi Warren, hi Ted,
sorry I was on holidays a couple of days last week and am completely behind
everything. Will try to have a look as soon as possible. Maybe Friday or next
week…
Mirja
> Am 09.10.2018 um 16:51 schrieb Warren Kumari :
>
> Mirja -- checking in again.
>
> W
>
> On Tue, Oct 2
39 matches
Mail list logo
