[sipcore] Barry Leiba's No Objection on draft-ietf-sipcore-locparam-05: (with COMMENT)
Barry Leiba via Datatracker <noreply@ietf.org> Wed, 05 February 2020 06:38 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 403CC120096; Tue, 4 Feb 2020 22:38:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sipcore-locparam@ietf.org, Jean Mahoney <mahoney@nostrum.com>, sipcore-chairs@ietf.org, mahoney@nostrum.com, sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <158088470322.15768.16507673259473509493.idtracker@ietfa.amsl.com>
Date: Tue, 04 Feb 2020 22:38:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ra_ZtcR8Hp9bJmW3AfOQYJP34Fo>
Subject: [sipcore] Barry Leiba's No Objection on draft-ietf-sipcore-locparam-05: (with COMMENT)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 05 Feb 2020 06:38:23 -0000
Barry Leiba has entered the following ballot position for draft-ietf-sipcore-locparam-05: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-sipcore-locparam/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I agree with Ben’s comments, and have only some editorial ones of my own to add: — Section 4 — Only a fully qualified host name is valid. The syntax does not support IP addresses, and if an entity conforming to this specification receives a Geolocation header field with a "loc-src" parameter containing an IP address then the parameter MUST be removed. It’s a small point, but as you’re already identifying a subject (“an entity conforming to this specification”), it’s unnecessarily awkward to use oassive voice: NEW Only a fully qualified host name is valid. The syntax does not support IP addresses, and if an entity conforming to this specification receives a Geolocation header field with a "loc-src" parameter containing an IP address, it MUST remove the parameter. END — Section 7 — This document introduces the ability of a SIP intermediary to insert a host name indicating that they added the specific locationValue to the Geolocation header field. Make it “indicating that it added”; there aren’t multiple intermediaries here. If such trust domain is not given, it is strongly recommended to delete the location information. I think the right fix to Ben’s comment here is “If a sufficient trust relationship does not exist, it is strongly recommended that the location information be deleted.”
- [sipcore] Barry Leiba's No Objection on draft-iet… Barry Leiba via Datatracker
- Re: [sipcore] Barry Leiba's No Objection on draft… R.Jesske
- Re: [sipcore] Barry Leiba's No Objection on draft… Barry Leiba