Re: [alto] 2nd WGLC draft-ietf-alto-new-transport (Ends 01/06/2023)

Hi all, The WGLC is now closed for the document. No objection/ major issues were raised against progressing this specification. However, there are few minor comments [1]/edits[2] that need to be addressed before we send the document to the IESG for publication. Authors, can you please prepare

[alto] 2nd WGLC draft-ietf-alto-oam-yang (Ends 06/06/2023)

Hi all, The authors believe that they addressed the comments raised during the 1st WGLC and also from the various directorate. The full set of resolved issues can be tracked at [1]. This message starts the second WGLC for the transport draft: https://datatracker.ietf.org/doc/draft-ietf-alto-oa

[alto] 2nd WGLC draft-ietf-alto-new-transport (Ends 01/06/2023)

Hi all, The authors believe that they addressed the comments raised during the 1st WGLC and also from the various directorate. This message starts the second WGLC for the transport draft: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/09/. The WGLC runs for one week, i.e., till

Re: [alto] IPJ article on ALTO

Hi all, FYI, the paper is also listed in the WG Datatracker page under "Additional resources": https://datatracker.ietf.org/wg/alto/about/. Cheers, Med De : alto De la part de Jordi Ros Giralt Envoyé : mardi 23 mai 2023 18:43 À : alto@ietf.org Objet : [alto] IPJ article on ALTO Hi ALTOers, H

Re: [alto] draft-ietf-alto-oam-yang : Call for volunteers to review 2nd WGLC for ALTO docs

Hi Jensen, all On this one : use draft-ietf-netmod-rfc6991-bis instead of RFC6991 I suggest we leave RFC6991 as in the current version and adjust in the future if the bis makes it before this one (which is not unlikely but who knows). Thanks. Cheers, Med De : alto De la part de Jensen Zhang

Re: [alto] [ietf-wg-alto/draft-ietf-alto-oam-yang] Security Considerations (Issue #33)

Hi Jensen, Please see inline. Cheers, Med De : Jensen Zhang Envoyé : jeudi 11 mai 2023 04:15 À : BOUCADAIR Mohamed INNOV/NET Cc : ietf-wg-alto/draft-ietf-alto-oam-yang ; IETF ALTO Objet : Re: [alto] [ietf-wg-alto/draft-ietf-alto-oam-yang] Security Considerations (Issue #33) Hi Med, Sorry

Re: [alto] [ietf-wg-alto/draft-ietf-alto-oam-yang] Security Considerations (Issue #33)

Hi Jensen, Thanks for drafting that text. I do still that some sensitive data nodes have to be listed. For example, * Access to all authentication-related data nodes should be protected; those that are inherited from other models have already “nacm:default-deny-write” statement, while the

[alto] Proposed Agenda for Interims #2-5

Hi all, Please find below the proposed agenda for the forthcoming interims * interim #2: WGLC follow-up of OAM/Transport I-Ds * interim #3: Deployment Catalysts * Reuse existing network resources to identify ALTO resources (e.g., BGP communities) * Proposals to fix the integration compl

Re: [alto] draft-ietf-alto-new-transport known implementations

Hi all, Forwarding to the list, fwiw. Cheers, Med De : Lachlan Keller Envoyé : vendredi 3 mars 2023 23:01 À : BOUCADAIR Mohamed INNOV/NET Cc : draft-ietf-alto-new-transp...@ietf.org; alto-cha...@ietf.org Objet : Re: draft-ietf-alto-new-transport known implementations Hello, There are no curr

Re: [alto] ALTO deployment wiki page updates

Hi Richard, Thank you for your effort. FWIW, I added a “related_implementations” tag to the ALTO Datatracker page so that the content you shared is easily accessed: https://datatracker.ietf.org/wg/alto/about/ Cheers, Med De : alto De la part de Y. Richard Yang Envoyé : jeudi 23 mars 2023 04:

Re: [alto] Discussion on the future of ALTO WG

Hi Jordi, all, Only some logistic comments, not reacting to any expressed views so far: * We created a page at https://github.com/ietf-wg-alto/wg-materials/blob/main/FutureALTO/alto-direction-of-work.md to track the various proposals (yours is posted there), challenge them, enrich them, a

[alto] Discussion on the future of ALTO WG

Hi all, As the WG is about to finalize the last chartered items, we would like to have a discussion on the future of the WG with all of you. We will also have a slot during the IETF#116 meeting on this matter. The plan is to let this discussion open for the coming two months (i.e., ** till end

Re: [alto] WGLC for draft-ietf-alto-new-transport (Ends 28/03/2023)

Hi Kai, I would use the mailing list given that very few are watching the GitHub activity. Thank you. Cheers, Med De : kai...@scu.edu.cn Envoyé : mardi 21 mars 2023 16:25 À : BOUCADAIR Mohamed INNOV/NET Cc : IETF ALTO ; draft-ietf-alto-new-transp...@ietf.org; ALTO Working Group Objet : Re:

Re: [alto] WGLC for draft-ietf-alto-new-transport (Ends 28/03/2023)

Hi all, This is a nudge that this WGLC is still running for one more week. So, please review and share your comments. FWIW, the current situation is as follows: * 11 Open WGLC Issues: https://github.com/ietf-wg-alto/draft-ietf-alto-new-transport/issues?q=is%3Aissue+is%3Aopen+label%3AWGLC

Re: [alto] WGLC for draft-ietf-alto-oam-yang (Ends 26/03/2023)

Hi all, This is a gentle reminder that this WGLC is still running. Silence does not mean that the document is in good shape. So, please review and share your comments. If you are happy with the current version, that's also a good feedback we would like to hear. FWIW, there are: * 5 Close

Re: [alto] [art] Second early ART ART review of draft-ietf-alto-new-transport (-07)

Hi Spencer, Thanks for providing the review in a timely manner. Much appreciated. Unless I’m mistaken, the review was not forwarded to the ALTO WG list. I’m adding the missing lists, fwiw. One quick comment on your previous comment about SETTINGS_ENABLE_PUSH, I remember the authors provided a

Re: [alto] Tsvart early review of draft-ietf-alto-new-transport-07

Hi Bernard, Many thanks for the prompt review. Much appreciated! To ease tracking the points you raised, I created three issues at https://github.com/ietf-wg-alto/draft-ietf-alto-new-transport/labels/tsvart. One of these points is related to a pending comment to clarify to what extent the cu

Re: [alto] WGLC for draft-ietf-alto-new-transport (Ends 28/03/2023)

Hi Luis, Yes, you are right. The correct link is: https://datatracker.ietf.org/doc/html/draft-ietf-alto-new-transport-07. Cheers, Med De : alto De la part de LUIS MIGUEL CONTRERAS MURILLO Envoyé : mardi 14 mars 2023 23:23 À : Qin Wu ; IETF ALTO Cc : ALTO Working Group Objet : Re: [alto] WGLC

Re: [alto] WGLC for draft-ietf-alto-new-transport (Ends 28/03/2023)

Hi all, WGLC comments can also be reported as github issues/PRs. Please use "WGLC" label when filling your issues/PR. FYI, the reported WGLC comments can be seen at: https://github.com/ietf-wg-alto/draft-ietf-alto-new-transport/issues?q=is%3Aissue+is%3Aopen+label%3AWGLC. Cheers, Med De : Qin

Re: [alto] WGLC for draft-ietf-alto-oam-yang (Ends 26/03/2023)

Re-, FWIW, issues/PRs may be also raised using the github repo. Please use "WGLC" label when entering your items. The current active WGLC comments can be seen at: https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues?q=is%3Aissue+is%3Aopen+label%3AWGLC Cheers, Med De : BOUCADAIR Moh

[alto] WGLC for draft-ietf-alto-oam-yang (Ends 26/03/2023)

Hi all, This message starts the WGLC for https://datatracker.ietf.org/doc/html/draft-ietf-alto-oam-yang-06. The call ends: 26/03/2023. Please review and indicate your support or objection to proceed with the publication of this document. Thank you. Cheers, Qin & Med

[alto] draft-ietf-alto-oam-yang implementations

Hi all, Can you please share details about any implementations you are aware of this draft? Thank you. Cheers, Med _ Ce message et ses pieces jointes peuvent contenir des inf

Re: [alto] IPR Poll: draft-ietf-alto-new-transport

Hi all, It seems that we have all replies expect from Lachlan and Lauren. Lauren/Lachlan, we would appreciate if you can reply to this poll in a timely manner. Thanks. Cheers, Med De : alto De la part de kai...@scu.edu.cn Envoyé : jeudi 2 mars 2023 09:10 À : Y. Richard Yang Cc : roland.sch..

[alto] IPR poll: draft-ietf-alto-oam-yang

Hi Authors, Please reply to this email (with the WG mailing list cced) indicating whether you are aware of any IPR related to draft-ietf-alto-oam-yang. If you are aware of any, can you please confirm that all appropriate IPR disclosures required for full conformance with the provisions of BCP 7

[alto] IPR Poll: draft-ietf-alto-new-transport

Hi Authors, Please reply to this email (with the WG mailing list cced) indicating whether you are aware of any IPR related to draft-ietf-alto-new-transport. If you are aware of any, can you please confirm that all appropriate IPR disclosures required for full conformance with the provisions of

Re: [alto] I-D Action: draft-ietf-alto-new-transport-05.txt

Hi Roland, Richard, Kai, and Lachlan, Thank you for preparing this revised version. Can you please share with the WG a summary/reasoning of major changes and a status of the pending issues for this spec? Thanks much for your effort. Cheers, Med > -Message d'origine- > De : I-D-Annou

Re: [alto] Presenting ALTO-related work at MOPS WG on Friday

Hi all, The slides that are presented by Luis can be seen at: https://datatracker.ietf.org/meeting/114/materials/slides-114-mops-exposure-of-telefonica-network-topology-through-alto-for-integration-with-telefonica-cdn/ Cheers, Med De : alto De la part de LUIS MIGUEL CONTRERAS MURILLO Envoyé :

Re: [alto] Cellular information exposure discussion (Fwd: New Version Notification for draft-huang-alto-mowie-for-network-aware-app-04.txt

Re-, Thank you, Yixue. BTW, as part of your SoA you may consider listing (analyzing?) some proposals that were made in the past to address similar issues, e.g., * https://datatracker.ietf.org/doc/html/draft-sprecher-mobile-tg-exposure-req-arch-03 * https://datatracker.ietf.org/doc/ht

Re: [alto] Cellular information exposure discussion (Fwd: New Version Notification for draft-huang-alto-mowie-for-network-aware-app-04.txt

Hi Eric, Richard, all, Thank you for sharing these details. FWIW, you may find some very few comments on the first part of the draft at: * pdf: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-huang-alto-mowie-for-network-aware-app-04-rev%20Med.pdf * doc: https://gith

Re: [alto] Cellular information exposure discussion (Fwd: New Version Notification for draft-huang-alto-mowie-for-network-aware-app-04.txt

Hi Richard, Thanks for this information. Just out of curiosity, are the proposed extensions currently discussed in the 3GPP? Cheers, Med De : alto De la part de Y. Richard Yang Envoyé : mardi 19 juillet 2022 20:14 À : IETF ALTO Objet : [alto] Cellular information exposure discussion (Fwd: Ne

[alto] Some comments about draft-lcsr-alto-service-functions-01

Hi Luis, Sabine, and Xufeng, Thank you for editing this draft. FWIW, you may find some comments at: * pdf: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-lcsr-alto-service-functions-01-rev%20Med.pdf * doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/

[alto] Some comments about draft-xing-alto-sdn-controller-aware-mptcp-mpquic

Hi Ziyang, all, Thank you for the effort put into this document. Really cool to see concrete proposals that use ALTO to feed a network intelligence. FWIW, you can find some comments to your draft at: * pdf: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-xing-alto-sdn-co

Re: [alto] I-D Action: draft-ietf-alto-new-transport-00.txt

Hi all, FWIW, we requested an early artart review to seek for feedback, particularly about the handling of versioning. We indicated 06/07 as target deadline so that comments can be digested, and hopefully a revised version is made available before the next IETF meeting. We prefer to have this

[alto] a separate document for HTTP/3 (was RE: WG adoption call for draft-schott-alto-new-transport-01)

Hi Adrian, Thank you for the review and comments. For the point about H3, we hope that at least common H2/H3 functionalities can be covered in this I-D. FWIW, we need to be careful about the versioning and keep in mind this part from RFC9205: == ... Requiring a particular version of HT

Re: [alto] Murray Kucherawy's Discuss on draft-ietf-alto-cost-mode-04: (with DISCUSS and COMMENT)

Re-, Deal! As you can see at https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-mode-05, went with a more verbose text to insist on this + add a MUST for implementations. Thanks. Cheers, Med De : Murray S. Kucherawy Envoyé : jeudi 2 juin 2022 08:58 À : BOUCADAIR Mohamed INNOV/NET Cc :

Re: [alto] Murray Kucherawy's Discuss on draft-ietf-alto-cost-mode-04: (with DISCUSS and COMMENT)

Hi Murray, Thanks for the review. Please see inline. Cheers, Med > -Message d'origine- > De : Murray Kucherawy via Datatracker > Envoyé : jeudi 2 juin 2022 08:16 > À : The IESG > Cc : draft-ietf-alto-cost-m...@ietf.org; alto-cha...@ietf.org; > alto@ietf.org; kai...@scu.edu.cn > Obj

Re: [alto] I-D Action: draft-ietf-alto-cost-mode-04.txt

Hi Martin, all, This version addresses the various IESG reviews. Cheers, Med > -Message d'origine- > De : alto De la part de internet- > dra...@ietf.org > Envoyé : jeudi 2 juin 2022 07:30 > À : i-d-annou...@ietf.org > Cc : alto@ietf.org > Objet : [alto] I-D Action: draft-ietf-alto-co

Re: [alto] Paul Wouters' Discuss on draft-ietf-alto-cost-mode-03: (with DISCUSS and COMMENT)

Hi Paul, Thank you for the review. Please see inline. Cheers, Med > -Message d'origine- > De : Paul Wouters via Datatracker > Envoyé : jeudi 2 juin 2022 05:12 > À : The IESG > Cc : draft-ietf-alto-cost-m...@ietf.org; alto-cha...@ietf.org; > alto@ietf.org; kai...@scu.edu.cn; kai...@s

Re: [alto] Roman Danyliw's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)

Hi Roman, I confirm. No designated expert is needed here. Thanks. Cheers, Med > -Message d'origine- > De : Roman Danyliw via Datatracker > Envoyé : mardi 31 mai 2022 17:43 > À : The IESG > Cc : draft-ietf-alto-cost-m...@ietf.org; alto-cha...@ietf.org; > alto@ietf.org; kai...@scu.edu.c

Re: [alto] Francesca Palombini's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)

Re-, Sure. Please use the same diff provided below to track the changes. Thanks. Cheers, Med De : Francesca Palombini Envoyé : mardi 31 mai 2022 15:24 À : BOUCADAIR Mohamed INNOV/NET ; The IESG Cc : draft-ietf-alto-cost-m...@ietf.org; alto-cha...@ietf.org; alto@ietf.org; kai...@scu.edu.cn O

Re: [alto] Francesca Palombini's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)

Hi Francesca, Thank you for the review. The names of the fields are self-descriptive, but no problem to add some text as you can see in the proposal at: https://tinyurl.com/cost-mode-latest Added a note for the "priv" case so that it is easily available from the IANA registry itself. Cheer

Re: [alto] Robert Wilton's Discuss on draft-ietf-alto-cost-mode-03: (with DISCUSS)

Hi Rob, FWIW, we added a NEW text to explain how the new modes can be discovered using legacy means: https://tinyurl.com/cost-mode-latest. Thanks for the review. Cheers, Med > -Message d'origine- > De : Robert Wilton via Datatracker > Envoyé : mercredi 25 mai 2022 17:06 > À : The I

Re: [alto] Lars Eggert's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)

Hi Lars, Thanks for the comment. Please see inline. Cheers, Med > -Message d'origine- > De : Lars Eggert via Datatracker > Envoyé : lundi 30 mai 2022 13:42 > À : The IESG > Cc : draft-ietf-alto-cost-m...@ietf.org; alto-cha...@ietf.org; > alto@ietf.org; kai...@scu.edu.cn; kai...@scu.ed

Re: [alto] Secdir last call review of draft-ietf-alto-cost-mode-03

Hi Stephen, Thank you for the review. I confirm. The part you quoted from Section 6.1.2 is still valid as is. Cheers, Med > -Message d'origine- > De : Stephen Farrell via Datatracker > Envoyé : jeudi 19 mai 2022 14:48 > À : sec...@ietf.org > Cc : alto@ietf.org; draft-ietf-alto-cost-m

Re: [alto] I-D Action: draft-ietf-alto-cost-mode-03.txt

Hi all, This version fixes a bug in the html version and some nits reported in the directorate reviews received so far. Cheers, Med > -Message d'origine- > De : I-D-Announce De la part de > internet-dra...@ietf.org > Envoyé : mardi 17 mai 2022 08:26 > À : i-d-annou...@ietf.org > Cc :

Re: [alto] [IANA #1230654] [Errata Verified] RFC7285 (6876)

Hi Amanda, all, The changes look good to me. Thank you for taking care of this. Cheers, Med > -Message d'origine- > De : Amanda Baber via RT > Envoyé : samedi 14 mai 2022 00:55 > À : rfc-edi...@rfc-editor.org > Cc : y...@cs.yale.edu; w.ro...@alcatel-lucent.com; > sprev...@cisco.com; sha

Re: [alto] Question on ANE name format

Hi Sabine, all, I would go personally for option 1. Thanks. Cheers, Med De : Randriamasy, Sabine (Nokia - FR/Paris-Saclay) Envoyé : lundi 9 mai 2022 18:20 À : IETF ALTO ; BOUCADAIR Mohamed INNOV/NET ; Qin (Bill) Wu ; martin.h.d...@gmail.com; zaheduzzaman.sar...@ericsson.com Cc : we...@wdroom

Re: [alto] Artart last call review of draft-ietf-alto-cost-mode-02

Hi Jaime, Thank you for the careful review. Please see inline. Cheers, Med > -Message d'origine- > De : Jaime Jimenez via Datatracker > Envoyé : mercredi 11 mai 2022 10:01 > À : a...@ietf.org > Cc : alto@ietf.org; draft-ietf-alto-cost-mode@ietf.org; last- > c...@ietf.org > Objet

Re: [alto] Genart last call review of draft-ietf-alto-cost-mode-02

Hi Roni, Thank you for the review. It will be ACKed in the next iteration of the draft. Cheers, Med > -Message d'origine- > De : Roni Even via Datatracker > Envoyé : samedi 7 mai 2022 13:39 > À : gen-...@ietf.org > Cc : alto@ietf.org; draft-ietf-alto-cost-mode@ietf.org; last- > c.

Re: [alto] Last Call: (A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol) to Proposed Standard

Hi Ben, Thank you for the comment. I think that you got the reasoning for not including such an encouragement text. BTW, I expect that the main concern will be related to modifying modes so that cost metrics are erroneously interpreted. That risk falls under 15.1 of 7285. Cheers, Med >

Re: [alto] Shepherd review for draft-ietf-alto-cost-mode-01

Hi Kai, I know that 7285 includes something similar, but the proposed text is redundant with the structure of the table in that section. I prefer to not include this text. Thank you. Cheers, Med > -Message d'origine- > De : kai...@scu.edu.cn > Envoyé : dimanche 17 avril 2022 16:08

Re: [alto] Shepherd review for draft-ietf-alto-cost-mode-01

Hi Kai, The changes are raisonnable. A new version that implements the changes edits is now online. Thanks. Cheers, Med > -Message d'origine- > De : kai...@scu.edu.cn > Envoyé : samedi 16 avril 2022 03:49 > À : alto@ietf.org > Cc : BOUCADAIR Mohamed INNOV/NET ; > Qin Wu > Objet :

Re: [alto] IPR Check for draft-ietf-alto-cost-mode-01

Hi Kai, all, I don't have any IPR nor I'm aware of any related to this draft. Cheers, Med > -Message d'origine- > De : alto De la part de kai...@scu.edu.cn > Envoyé : mardi 12 avril 2022 09:08 > Cc : alto@ietf.org > Objet : [alto] IPR Check for draft-ietf-alto-cost-mode-01 > > Dear aut

Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Kai, all, These RFCs are referring to Unicode in general, where several hyphens are supported. RFC7285 points explicitly to US-ASCII alphanumeric characters, where U+002D is the only hyphen: * There is no ambiguity about the intended behavior given that U+002D is provided * Even if we reaso

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Hi all, This message concludes this call for adoption. Given the fair amount of support and that no objection was made, the draft is adopted. Authors, please submit the draft as draft-ietf-alto-oam-yang at your convenience. The -00 is pre-validated. No need to reflect the comments from Qiufan

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

Hi Sebastien, I can't act on the erratum to update the "Corrected Text" to reflect what we agreed together. I guess Martin or the RFC editor can make that update and then mark it as verified. Doing so would allow the corrected text to be seen as part of the rendered RFC version (https://www.

Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Peng, Thank you for the comment. Not sure what you meant by “optimization” of that section. There are many cost metrics that were defined since then, including hopcount initially mentioned in 7285. See for example: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics#s

Re: [alto] Call for adoption: draft-zhang-alto-oam-yang

Hi all, This is a reminder that this call for adoption is still running. Cheers, Qin & Med De : mohamed.boucad...@orange.com Envoyé : mercredi 23 mars 2022 14:45 À : alto@ietf.org; draft-zhang-alto-oam-y...@ietf.org Cc : alto-cha...@ietf.org Objet : Call for adoption: draft-zhang-alto-oam-yang

[alto] IPR Poll for draft-zhang-alto-oam-yang

Hi all, You are listed as a co-author of draft-zhang-alto-oam-yang currently under call for adoption in ALTO WG. Please reply to this email (with the WG mailing list cced) indicating whether you are aware of any IPR related to draft-zhang-alto-oam-yang. If you are aware of any, please confirm

[alto] Call for adoption: draft-zhang-alto-oam-yang

Hi all, As discussed during the IETF#113 meeting, this message initiates the call for adoption of draft-zhang-alto-oam-yang to meet the following ALTO WG milestone: == Dec 2022ALTO OAM Document/YANG Model == Please reply to this message indicating your support or objection to adopt the doc

Re: [alto] Benjamin Kaduk's No Objection on draft-ietf-alto-performance-metrics-26: (with COMMENT)

Hi Ben, Thank you much for checking the updates and for all your effort to enhance IETF specs. That’s highly appreciated. One more revision is still needed before we declare this document ready to move forward: address a comment from Éric about TCP-centric metrics. -27 will be published very

Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi Sabine, Good catches and suggestions. Fixed as you can see in https://github.com/boucadair/alto-cost-mode/commit/08dacba1ae6e108bdb8ce2f7a0402bf4f04144eb. https://tinyurl.com/alto-cost-mode-latest provides the full diff. Thank you. Cheers, Med De : Randriamasy, Sabine (Nokia - FR/Paris-Sa

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

Hi Sebastien, all, Works for me. Thanks. Cheers, Med > -Message d'origine- > De : Sebastian Kiesel > Envoyé : jeudi 10 mars 2022 13:17 > À : Chris Smiley > Cc : martin.h.d...@gmail.com; Zaheduzzaman Sarker > ; BOUCADAIR Mohamed INNOV/NET > ; ral...@google.com; repe...@cisco.com; > y.

Re: [alto] [Editorial Errata Reported] RFC7285 (6874)

Re-, Works for me, thanks. Cheers, Med PS: The note is redundant with this text in 14.2, but that's OK as the note is intended to be echoed in the IANA registry: As specified in Section 10.6, identifiers prefixed with "priv:" are reserved for Private Use. > -Message d'origine-

Re: [alto] [Editorial Errata Reported] RFC7285 (6874)

Re-, Please see inline. Cheers, Med > -Message d'origine- > De : Sebastian Kiesel > Envoyé : mercredi 9 mars 2022 10:47 > À : BOUCADAIR Mohamed INNOV/NET > Cc : Chris Smiley ; martin.h.d...@gmail.com; > Zaheduzzaman Sarker ; > ral...@google.com; repe...@cisco.com; y...@cs.yale.edu; >

Re: [alto] [Editorial Errata Reported] RFC7285 (6876)

Hi Dhruv, I guess you also noticed that we don’t have such entry for the new created subregistries (while there is a provision for priv prefix for those as well in the spec): * https://www.iana.org/assignments/alto-protocol/alto-protocol.xhtml#alto-entity-domain-type * https://www.ian

Re: [alto] [Editorial Errata Reported] RFC7285 (6874)

Hi Sebastien, "priv:" is not an identifier per se and as such it should not be listed in that table. There is no change of the assignment policy in the errata. FWIW, the proposed changed was triggered by a comment "about consistency" we received for draft-bw-alto-cost-mode. As a Chair, I pre

Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi Luis, Re-, Dhruv, Thank you for sharing your thoughts. I wasn’t against “enabling private use”, but was not sure that having a dedicated prefix will stop from using other values that match local templates (e.g., prefix with a PEN) and which would achieve the same objective. I hear the consi

Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi Dhruv, Thank you for the comments. We will be adding a “description” in the next iteration, however the details about the structure/etc should not be echoed in the table but be available in the pointer provided under “Specification”. I’m not sure a specific prefix for private use is needed,

Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Re-, Good points, Adrian. These (except removing the pointer to Section 4.8 of 8126) will be fixed in the next version. Thank you. Cheers, Med > -Message d'origine- > De : Adrian Farrel > Envoyé : lundi 7 mars 2022 13:06 > À : kai...@scu.edu.cn; alto@ietf.org; alto-cha...@ietf.org >

Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi Kai, Thank you for taking care of the call. FWIW, I don't have any IPR related to this draft. Cheers, Med > -Message d'origine- > De : alto De la part de kai...@scu.edu.cn > Envoyé : lundi 7 mars 2022 12:28 > À : alto@ietf.org; alto-cha...@ietf.org > Objet : [alto] Call for Adopt

Re: [alto] [sfc] New Version Notification for draft-lachos-multi-domain-sfc-alto-00.txt

Dear Danny, Thank you for sharing this draft. My main comments about this draft are as follows: · The SFC WG is currently scoped to one single administrative domain. Even for the work we have done about hierarchical SFC, the assumption is that sub-domains are managed by the same admini