Re: [sipcore] news from draft-winterbottom-sipcore-locparam-02.txt
"A. Jean Mahoney" <mahoney@nostrum.com> Tue, 31 July 2018 18:30 UTC
Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97FC8130E75 for <sipcore@ietfa.amsl.com>; Tue, 31 Jul 2018 11:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.02
X-Spam-Level:
X-Spam-Status: No, score=0.02 tagged_above=-999 required=5 tests=[T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fct4YMTA6aMv for <sipcore@ietfa.amsl.com>; Tue, 31 Jul 2018 11:30:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F06A130F35 for <sipcore@ietf.org>; Tue, 31 Jul 2018 11:30:32 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.17.148]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6VIUU9d060383 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 31 Jul 2018 13:30:31 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.17.148] claimed to be mutabilis-2.local
To: R.Jesske@telekom.de, sipcore@ietf.org
References: <trinity-2fc5b505-6db8-4952-9443-66779e6b41fc-1530904253496@msvc-mesg-web002> <859713b7-85db-b366-8d5c-842e21f48992@nostrum.com> <FRXPR01MB0135AD2B7823671F5AE75EB7F92E0@FRXPR01MB0135.DEUPRD01.PROD.OUTLOOK.DE>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <bc9916c6-4079-42d7-ed27-9698f01d82ab@nostrum.com>
Date: Tue, 31 Jul 2018 13:30:29 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <FRXPR01MB0135AD2B7823671F5AE75EB7F92E0@FRXPR01MB0135.DEUPRD01.PROD.OUTLOOK.DE>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/SCtZgBG0SfvDZJYwnxlDONDC-yA>
Subject: Re: [sipcore] news from draft-winterbottom-sipcore-locparam-02.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2018 18:30:34 -0000
Hi Roland, Please create a version named draft-ietf-sipcore-locparam-00. Thanks! Jean On 7/31/18 2:37 AM, R.Jesske@telekom.de wrote: > Hi Jean, > I have seen that we have received support for adopting the draft. > Since seen my point of view sufficient support was expressed, I see that we can proceed with the draft. > I'm willing to discuss and consider in updating the draft based on the issues mentioned in the two mails from Olle and of course all other comments coming in. > > So my question is if we can proceed and I can then prepare a new draft. > > Thank you and Best Regards > > Roland > >> -----Ursprüngliche Nachricht----- >> Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von A. Jean >> Mahoney >> Gesendet: Dienstag, 10. Juli 2018 00:00 >> An: sipcore@ietf.org >> Betreff: Re: [sipcore] news from draft-winterbottom-sipcore-locparam- >> 02.txt >> >> Hi Roland, >> >> I went back through the comments on version -02, and found feedback on >> the Privacy Considerations and Security Considerations sections that has not >> yet been incorporated (What happens when an entity other than a phone >> adds a location, definition of a trusted network, Security Considerations of >> RFC 6442 out-of-date, etc.) >> >> That said, we can still ask the WG if they want to adopt the draft, and the >> draft can still be updated. >> >> Thanks, >> >> Jean >> >> >> On 7/6/18 2:10 PM, Roland Jesske wrote: >>> Hi, >>> We had around 12 month ago the discussion about the draft and had a >>> couple of comments which were addressed. >>> I see that this draft is ready for further proceeding since all >>> comments are solved. >>> Best Regards >>> Roland >>> -- >>> Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE >>> <http://WEB.DE> Mail gesendet. >>> Am 06.07.18, 20:45, Paul Kyzivat <pkyzivat@alum.mit.edu> schrieb: >>> >>> On 7/6/18 2:19 PM, A. Jean Mahoney wrote: >>> > Hi Andy, >>> > >>> > No update on the status because the chairs were waiting for some >>> of the >>> > other drafts to move along before coming back to this. And this >>> chair >>> > didn't catch that the draft was no longer expired. Revisions to >>> > individual drafts don't cause automatic notifications, so it's >>> best if >>> > authors send a note to the list when there is a new version. >>> > >>> > A question to the reviewers who provided feedback on -02, does -03 >>> > address your input? >>> >>> Yes, it addresses my concern. >>> >>> Thanks, >>> Paul >>> >>> > https://datatracker.ietf.org/doc/draft-winterbottom-sipcore- >> locparam/ >>> > >>> > Thanks! >>> > >>> > Jean >>> > >>> > >>> > On 7/6/18 4:37 AM, Andy Hutton wrote: >>> >> Just wondering why >>> >> >>> https://tools.ietf.org/html/draft-winterbottom-sipcore-locparam-03 had >>> >> not been adopted yet. >>> >> >>> >> Any update on status? >>> >> >>> >> Regards >>> >> Andy >>> >> On Wed, 18 Apr 2018 at 14:23, <bruno.chatras@orange.com> wrote: >>> >>> >>> >>> Are there any news about >>> draft-winterbottom-sipcore-locparam-02.txt. >>> >>> The last mail I have seen on that subject was sent on October >>> 2017. >>> >>> Are there remaining open issues? >>> >>> >>> >>> Bruno >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> ______________________________________________________________ >> ________ >>> ___________________________________________________ >>> >>> >>> >>> >>> >>> >>> 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. >>> >>> >>> >>> _______________________________________________ >>> >>> sipcore mailing list >>> >>> sipcore@ietf.org >>> >>> https://www.ietf.org/mailman/listinfo/sipcore >>> >> >>> >> _______________________________________________ >>> >> sipcore mailing list >>> >> sipcore@ietf.org >>> >> https://www.ietf.org/mailman/listinfo/sipcore >>> >> >>> > >>> > _______________________________________________ >>> > sipcore mailing list >>> > sipcore@ietf.org >>> > https://www.ietf.org/mailman/listinfo/sipcore >>> > >>> >>> _______________________________________________ >>> sipcore mailing list >>> sipcore@ietf.org >>> https://www.ietf.org/mailman/listinfo/sipcore >>> >>> >>> >>> _______________________________________________ >>> sipcore mailing list >>> sipcore@ietf.org >>> https://www.ietf.org/mailman/listinfo/sipcore >>> >> >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore
- Re: [sipcore] news from draft-winterbottom-sipcor… A. Jean Mahoney
- Re: [sipcore] news from draft-winterbottom-sipcor… A. Jean Mahoney
- Re: [sipcore] news from draft-winterbottom-sipcor… A. Jean Mahoney
- Re: [sipcore] news from draft-winterbottom-sipcor… A. Jean Mahoney
- Re: [sipcore] news from draft-winterbottom-sipcor… Roland Jesske
- Re: [sipcore] news from draft-winterbottom-sipcor… Roland Jesske
- Re: [sipcore] news from draft-winterbottom-sipcor… Paul Kyzivat
- Re: [sipcore] news from draft-winterbottom-sipcor… Andy Hutton
- [sipcore] news from draft-winterbottom-sipcore-lo… bruno.chatras
- Re: [sipcore] news from draft-winterbottom-sipcor… R.Jesske
- Re: [sipcore] news from draft-winterbottom-sipcor… A. Jean Mahoney