Re: [Drip] (reminder) RE: call for adoption for draft-ietf-drip-uas-rid

Hi Alex, 

If you check https://datatracker.ietf.org/group/drip/documents/, you will see that the document is ** not listed ** as a WG item. The status is set to "I-D Exists Candidate for WG Adoption".

I reiterate what we already said in the note sent to the WG: If there is no sufficient support for adoption, we will change the state in the data tracker accordingly (e.g., "dead"). 

The adoption call is meant to mainly assess the followings: 

(1) Is the document a good starting point to deliver what the WG promised in the charter?
==
Sep 2020 Solution space documents adopted by the WG
==
(2) is there enough energy to contribute/review the document?
(3) Is the proposed solution broken and issues can't be fixed?

The WG may consider more than one solution document. 

Hope this clarifies your concerns. 

Cheers,
Med

> -----Message d'origine-----
> De : Tm-rid [mailto:tm-rid-bounces@ietf.org] De la part de Alexandre
> Petrescu
> Envoyé : jeudi 17 septembre 2020 15:35
> À : tm-rid@ietf.org
> Objet : Re: [Drip] (reminder) RE: call for adoption for draft-ietf-
> drip-uas-rid
> 
> I dont know how to shar emy thoughts.
> 
> You say that we need to comment on the contents, not on the naming.
> 
> I could comment on the content if there was the right name.
> 
> But the wrong name implies that the comments are not needed.  The
> name is wrong in that it seems to be adopted, so there would be no
> need of comments.
> 
> If the name was right, and the document was not adopted, and if
> there was a chance for the document to _not_ be adopted, then I
> could comment on it.  Otherwise, why should I comment on it if it is
> already adopted?
> 
> My comment is around the following:
> 
> Is UAS-RID concept decoupled from the use of HIP?  Or does UAS-RID
> mandate the use of HIP?
> 
> Because, there are other ways into which to achieve same effects as
> HIP which might be probably more in use in the Internet today.  Or
> maybe there are implementations aspects of HIP that I am not aware
> of.
> 
> These are my comments to a document whose name seems to not need
> comments.
> 
> This is a long email, as the situation is difficult.
> 
> Alex
> 
> Le 16/09/2020 à 08:17, mohamed.boucadair@orange.com a écrit :
> > Re,
> >
> > This s a nudge that the call is still open for one week.
> >
> > Silence does not mean support. So, please consider sharing your
> > thoughts about this draft and whether it should be adopted or not
> to
> > meet this
> > milestone:
> >
> > =====
> >
> > Sep 2020 Solution space documents adopted by the WG
> >
> > =====
> >
> > Cheers,
> >
> > Daniel & Med
> >
> > *De :*Tm-rid [mailto:tm-rid-bounces@ietf.org] *De la part de*
> Daniel
> > Migault *Envoyé :* mercredi 9 septembre 2020 19:04 *À :*
> > tm-rid@ietf.org *Objet :* [Drip] call for adoption for
> > draft-ietf-drip-uas-rid
> >
> > Hi,
> >
> > This email starts a call for adoption for draft-ietf-drip-uas-rid
> > available here:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-drip-uas-rid/
> >
> > The call for adoption ends on 2020 September 23.  Please state
> clearly
> > your opinion whether you think the work should be adopted or not.
> If
> > you think the work should not be adopted, please state why.
> >
> > Yours,
> > Med and Daniel
> >
> > --
> >
> > Daniel Migault
> >
> > Ericsson
> >
> >
> ____________________________________________________________________
> __
> > ___________________________________________________
> >
> > 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.
> >
> >
> 
> --
> Tm-rid mailing list
> Tm-rid@ietf.org
> https://www.ietf.org/mailman/listinfo/tm-rid

_________________________________________________________________________________________________________________________

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.