Re: [sipcore] New Version Notification for draft-winterbottom-sipcore-locparam-02.txt

What are the next steps to get this document approved as an RFC? Is there anything missing? On the ETSI side we do need to reference this document from an ETSI standard that will be published very soon.
Bruno
-----Message d'origine-----
De : sipcore [mailto:sipcore-bounces@ietf.org] De la part de Jesske, Roland
Envoyé : mardi 24 octobre 2017 11:25
À : sipcore@ietf.org
Objet : [sipcore] WG: New Version Notification for draft-winterbottom-sipcore-locparam-02.txt

Dear all,
last week I have updated draft-winterbottom-sipcore-locparam due to the discussions made.
So all comments made are now reflected.
I did some improvement of the text with regard to the use of the locparam within the trusted domain.
This reflects the use to be intended within a trust domain.

Thank you and Best Regards

Roland 

-----Ursprüngliche Nachricht-----
Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Gesendet: Donnerstag, 19. Oktober 2017 05:44
An: Andrew Hutton <andrew.hutton@unify.com>; Jesske, Roland <R.Jesske@telekom.de>; James Winterbottom <a.james.winterbottom@gmail.com>; Bruno Chatras <bruno.chatras@orange.com>
Betreff: New Version Notification for draft-winterbottom-sipcore-locparam-02.txt

A new version of I-D, draft-winterbottom-sipcore-locparam-02.txt
has been successfully submitted by Roland Jesske and posted to the IETF repository.

Name:		draft-winterbottom-sipcore-locparam
Revision:	02
Title:		Location Source Parameter for the SIP Geolocation Header Field
Document date:	2017-10-18
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/internet-drafts/draft-winterbottom-sipcore-locparam-02.txt
Status:         https://datatracker.ietf.org/doc/draft-winterbottom-sipcore-locparam/
Htmlized:       https://tools.ietf.org/html/draft-winterbottom-sipcore-locparam-02
Htmlized:       https://datatracker.ietf.org/doc/html/draft-winterbottom-sipcore-locparam-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-winterbottom-sipcore-locparam-02

Abstract:
   There are some circumstances where a geolocation header field may
   contain more than one location value.  Knowing the identity of the
   node adding the location value allows the recipient more freedom in
   selecting the value to look at first rather than relying solely on
   the order of the location values.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

_________________________________________________________________________________________________________________________

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.