Re-,
Please see inline.
Cheers,
Med
> Zahed,
>
>
>
> It is a matter of balance between what the WG can successfully deliver vs.
> exhaustiveness. Proceeding in steps (having first a base module + including
> provision to graft extension) is pragmatic given the limited resources of
> the WG.
>
On Thu, Oct 26, 2023 at 3:58 PM wrote:
> Zahed,
>
>
>
> It is a matter of balance between what the WG can successfully deliver vs.
> exhaustiveness. Proceeding in steps (having first a base module + including
> provision to graft extension) is pragmatic given the limited resources of
> the WG.
>
Zahed,
It is a matter of balance between what the WG can successfully deliver vs.
exhaustiveness. Proceeding in steps (having first a base module + including
provision to graft extension) is pragmatic given the limited resources of the
WG.
Please note that the spec relies upon common reusable
Okay, so in fact both forms of the NAPTR value are going to be used as a
DNS owner name. Either the owner name will be generated as an IN-ADDR
string based on the ip address, or it is represented literally? If so, it
would certainly make sense to say that explicitly to help the reader
connect that
On Thu, Oct 26, 2023 at 1:19 PM wrote:
> Hi Zahed,
>
> Please see inline.
>
> Cheers,
> Med
>
> > -Message d'origine-
> > De : Zaheduzzaman Sarker via Datatracker
> > Envoyé : jeudi 26 octobre 2023 13:12
> > À : The IESG
> > Cc : draft-ietf-alto-oam-y...@ietf.org; alto-cha...@ietf.org;
Hi Ted,
Thanks for the comments on the NAPTR-related part. It is very helpful.
To be more concrete, this "rdns-naptr-records" YANG node is to configure
DNS for the U-NAPTR lookup suggested by Sec 3.4 of RFC 8686 (
https://datatracker.ietf.org/doc/html/rfc8686#name-step-3-perform-dns-u-naptr-).
Hi all,
Normally, idnits flags when addresses are not documentation ones but fails to
find the one reported by Tom [1].
Thanks Tom.
Cheers,
Med
[1]
https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-15.txt=True
De : alto De la part de
Hi Tom,
Many thanks for following up on this document. Sorry to miss the issues.
We have fixed them in
https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/pull/100 and will
merge the changes to the next revision.
Thanks,
Jensen
On Thu, Oct 26, 2023 at 7:25 PM tom petch wrote:
> I
Hi Roman,
Many thanks for all the comments. Please see my responses inline below.
Thanks,
Jensen
On Wed, Oct 25, 2023 at 12:23 AM Roman Danyliw via Datatracker <
nore...@ietf.org> wrote:
> Roman Danyliw has entered the following ballot position for
> draft-ietf-alto-oam-yang-15: Discuss
>
>
I commented on this I-D 25sep23.
I got a response from the document shepherd which addressed two of my points
but not the others. I never got a response from an author.
I note that -15 still has issues that I raised. Two I notice are:
RFC9274 is in the text but not in the I-D References
Hi Zahed,
Please see inline.
Cheers,
Med
> -Message d'origine-
> De : Zaheduzzaman Sarker via Datatracker
> Envoyé : jeudi 26 octobre 2023 13:12
> À : The IESG
> Cc : draft-ietf-alto-oam-y...@ietf.org; alto-cha...@ietf.org;
> alto@ietf.org; BOUCADAIR Mohamed INNOV/NET
> ; BOUCADAIR
Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-alto-oam-yang-15: 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
Hi Rob,
On your comment about implems, there was the effort documented in the writeup:
https://github.com/IETF-Hackathon/ietf116-project-presentations/blob/main/alto-new-transport-presentation.pdf
I'm not aware of other implems of the spec.
Cheers,
Med
> -Message d'origine-
> De :
Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-alto-new-transport-17: 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
Robert Wilton has entered the following ballot position for
draft-ietf-alto-new-transport-17: 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
Robert Wilton has entered the following ballot position for
draft-ietf-alto-oam-yang-15: Yes
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
Murray Kucherawy has entered the following ballot position for
draft-ietf-alto-new-transport-17: 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
17 matches
Mail list logo
