Re: [alto] Robert Wilton's No Objection on draft-ietf-alto-new-transport-17: (with COMMENT)

[[e-mail]]

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 : Robert Wilton via Datatracker <[e-mail]>
> Envoyé : jeudi 26 octobre 2023 12:15
> À : The IESG <[e-mail]>
> Cc : [e-mail]; [e-mail];
> [e-mail]; BOUCADAIR Mohamed INNOV/NET
> <[e-mail]>; BOUCADAIR Mohamed INNOV/NET
> <[e-mail]>
> Objet : Robert Wilton's No Objection on draft-ietf-alto-new-transport-
> 17: (with COMMENT)
> 
> 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 to
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-
> positions%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C88604dc7e
> 34840ebb95f08dbd60c778e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
> 38339121249105754%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g6CAMT5s8
> Oag5xLtjEOsG%2FUUnGv%2FSfn29gZaKS%2Bcyy4%3D&reserved=0
> for more information about how to handle DISCUSS and COMMENT
> positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
> tracker.ietf.org%2Fdoc%2Fdraft-ietf-alto-new-
> transport%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C88604dc7e
> 34840ebb95f08dbd60c778e%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6
> 38339121249105754%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ViL5eZmqa
> NjveyxQVKc7AT0bo2ZjV4l%2FTwJvCFDX%2BBM%3D&reserved=0
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Hi,
> 
> Thank you for this document.  I haven't reviewed this document that
> closely,
> and it might be interesting to know whether there are interoperable
> implementations of this specification, or where there may still be
> issues
> lurking, or more precise text to describe its behavior and APIs.
> Hence, I was
> wondering whether it would be better from this document to be
> published as an
> experimental RFC rather than Proposed Standard, this would then leave
> a lot
> more flexibility for making more substantial changes to the protocol
> specification in future, if needed.
> 
> Regards,
> Rob
> 
> 

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.