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

<R.Jesske@telekom.de> Tue, 23 May 2017 13:05 UTC

Return-Path: <prvs=30986142b=R.Jesske@telekom.de>
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 8B9E0129A9F for <sipcore@ietfa.amsl.com>; Tue, 23 May 2017 06:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 TactIiUAKCNY for <sipcore@ietfa.amsl.com>; Tue, 23 May 2017 06:05:08 -0700 (PDT)
Received: from MAILOUT21.telekom.de (MAILOUT21.telekom.de [80.149.113.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21F6A129B2B for <sipcore@ietf.org>; Tue, 23 May 2017 06:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1495544708; x=1527080708; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QzBovQ3FlOOfcEfRolwGLrx+IumDUjsJtQTk/+ia9u8=; b=lf3fVP+llo7AKjQLFFR1dm+rNprseyKzkoaTIi1H0l8xfz1Ki6tXilSa veR21cXE5VRBq/WeS6vULuSRhUF7lzHKDtrGj9eZ15bBuBO0JVNPXcSx3 urzIeRRmvzQj/ZvPMUUiVUav6L+rC888hnUnASc/BTqoMa96eSSb9Gjvt 0lfSKNRImwnFefjTKYhu35OWAO/O/8Pq6JqbcLh2U1eoUaMCz7uRsgpWx JdGCEDirkyk7upQuq/ViaI7An4c6Hz3DT1KYhCvUwJuZ03JL+FdNoX2AM ACuAJjxP8zAPhzNSpigRG5aJ+SRCoAztHfWwrp0zlAdRYwbRpH6xoDrxL A==;
Received: from q4de8psa04t.blf.telekom.de ([10.151.13.130]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 May 2017 15:04:51 +0200
X-IronPort-AV: E=Sophos;i="5.38,382,1491256800"; d="scan'208";a="674651645"
Received: from he105831.emea1.cds.t-internal.com ([10.169.119.34]) by Q4DE8PSA04V.blf.telekom.de with ESMTP/TLS/AES256-SHA; 23 May 2017 15:04:51 +0200
Received: from HE105828.EMEA1.cds.t-internal.com (10.169.119.31) by HE105831.emea1.cds.t-internal.com (10.169.119.34) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 23 May 2017 15:04:50 +0200
Received: from HE105828.EMEA1.cds.t-internal.com ([fe80::753e:c05:6c77:b585]) by HE105828.emea1.cds.t-internal.com ([fe80::753e:c05:6c77:b585%26]) with mapi id 15.00.1263.000; Tue, 23 May 2017 15:04:50 +0200
From: R.Jesske@telekom.de
To: sipcore@ietf.org
CC: bruno.chatras@orange.com, a.james.winterbottom@gmail.com, andrew.hutton@unify.com
Thread-Topic: New Version Notification for draft-winterbottom-sipcore-locparam-01.txt
Thread-Index: AQHS08JpUig+mkZVLEKjpPL+YXPfRqIB3WVA
Date: Tue, 23 May 2017 13:04:50 +0000
Message-ID: <159c97974a8749d4ab71016f57a768db@HE105828.emea1.cds.t-internal.com>
References: <149554350753.16443.17633151256632718640.idtracker@ietfa.amsl.com>
In-Reply-To: <149554350753.16443.17633151256632718640.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.213.236.246]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/tTcUY1e7FJXrHm_qy4CSTBKx3qg>
Subject: Re: [sipcore] New Version Notification for draft-winterbottom-sipcore-locparam-01.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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, 23 May 2017 13:05:11 -0000

Dear all,

After reworking the draft due to the comments made by Dale, I have uploaded a new version
https://www.ietf.org/internet-drafts/draft-winterbottom-sipcore-locparam-01.txt

I didn't get any comments on my answers given to Dales mail which also covered the comments made within the meeting report.

ETSI is still looking forward on processing this document for their solution on Emergency Call due to the Project of  the European Union Mandate: M493.
 
Comments and improvements are welcome.

Question is how to proceed further since I did not get any further comments since my last mail on 4th April.

Best Regards

Roland

> -----Ursprüngliche Nachricht-----
> Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Gesendet: Dienstag, 23. Mai 2017 14:45
> An: Jesske, Roland; Bruno Chatras; James Winterbottom; Andrew Hutton
> Betreff: New Version Notification for draft-winterbottom-sipcore-
> locparam-01.txt
> 
> 
> A new version of I-D, draft-winterbottom-sipcore-locparam-01.txt
> has been successfully submitted by Roland Jesske and posted to the IETF
> repository.
> 
> Name:		draft-winterbottom-sipcore-locparam
> Revision:	01
> Title:		Location Source Parameter for the SIP Geolocation
> Header Field
> Document date:	2017-05-23
> Group:		Individual Submission
> Pages:		8
> URL:            https://www.ietf.org/internet-drafts/draft-winterbottom-
> sipcore-locparam-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-winterbottom-
> sipcore-locparam/
> Htmlized:       https://tools.ietf.org/html/draft-winterbottom-sipcore-
> locparam-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-
> winterbottom-sipcore-locparam-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-winterbottom-
> sipcore-locparam-01
> 
> 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