RE: Spin bit discussion - where we're at

[<[e-mail]>]

Hi

I propose to contribute as a telco representative. We already described troubleshooting use cases in https://tools.ietf.org/html/draft-stephan-quic-interdomain-troubleshooting-00.

Regards
Emile

De : QUIC [mailto:[e-mail]] De la part de Roni Even
Envoyé : jeudi 23 novembre 2017 07:09
À : Marcus Ihlar; Eggert, Lars
Cc : Salvatore Loreto; Brian Trammell; Mark Nottingham; QUIC WG
Objet : RE: Spin bit discussion - where we're at

Hi,
I will work with Brian and Marcus on this draft
Roni

From: QUIC [mailto:[e-mail]] On Behalf Of Marcus Ihlar
Sent: יום ד 22 נובמבר 2017 17:58
To: Eggert, Lars
Cc: Salvatore Loreto; Brian Trammell; Roni Even; QUIC WG; Mark Nottingham
Subject: Re: Spin bit discussion - where we're at

Hi,
Just chipping in to say that I’m happy to work with Brian on this draft.

/Marcus

On 22 Nov 2017, at 22:51, Eggert, Lars <[e-mail]<mailto:[e-mail]>> wrote:
Hi,

On 2017-11-22, at 15:22, Roni Even <[e-mail]<mailto:[e-mail]>> wrote:
I think the decision to not discuss it at the interim is based on the observation
that the registered attendees at the interim are probably not representative
of the overall WG constituency - we want to give all sides an ability to
participate equally in the discussion.
[Roni Even] This is why we have remote participants at IETF meetings !!!!!!!!
You do not have to be in person to discuss!!!!

the IETF (vie MeetEcho) provides remote participation at the main meetings. At the interims, it's Mark. It seems to have mostly worked OK for passive participation during two out of the last three interims, but we haven't tried to hold a discussion with many active remote participants.

I think what Mark tried to express is that the discussion on the Spin Bit can be
mostly decoupled from the (large amount of) work remaining on the base
spec. That is, we don't have to conclude the Spin Bit discussion significantly
prior to the conclusion of the overall work (although we can), since it should
be easy to merge at the later stages before handing things to the IESG.
[Roni Even] delaying the discussion may prevent the acceptance.  If people will put effort at submitting text then the chairs should allow for discussion and not delay the work.

I disagree with this characterization.

What I said above in the paragraph you quote is that we do not *have to* conclude the Spin Bit discussion urgently *although we can*. Specifically, we can begin (and conclude) the discussion once there is an actual proposal that addresses what Mark's original email outlined.

Lars

_________________________________________________________________________________________________________________________

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.