[Ecrit] DISCUSS on draft-ietf-ecrit-location-hiding-req

"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Sun, 21 February 2010 07:27 UTC

Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34F3528C0D8 for <ecrit@core3.amsl.com>; Sat, 20 Feb 2010 23:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level:
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8GQbVfRqWoxF for <ecrit@core3.amsl.com>; Sat, 20 Feb 2010 23:27:00 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 0A16C28C0CF for <ecrit@ietf.org>; Sat, 20 Feb 2010 23:26:59 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o1L7Slxb016658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 21 Feb 2010 08:28:47 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o1L7SlKn027235; Sun, 21 Feb 2010 08:28:47 +0100
Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Sun, 21 Feb 2010 08:28:46 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 21 Feb 2010 09:27:19 +0200
Message-ID: <3D3C75174CB95F42AD6BCC56E5555B450238916D@FIESEXC015.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: DISCUSS on draft-ietf-ecrit-location-hiding-req
Thread-Index: Acqya3XpdZhB1FyqT8O5XHqIErjj1g==
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-OriginalArrivalTime: 21 Feb 2010 07:28:46.0858 (UTC) FILETIME=[8127B6A0:01CAB2C7]
Cc: ecrit@ietf.org
Subject: [Ecrit] DISCUSS on draft-ietf-ecrit-location-hiding-req
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2010 07:27:01 -0000

Hi Dan, 

You wrote: 
"
I like the document and I belive that it's ready for approval, but I
have a
rather minor detail to clarify.

 Req-6:  The solution MUST work if PSAP boundaries have holes.  (For a
      discussion about holes in PSAP boundaries and their encoding the
      reader is referred to [I-D.ietf-ecrit-specifying-holes].)

I do not see how the requirement can be understood without understanding
the
concept of holes in PSAP or LoST service boundaries. This being a MUST
requirement it looks to me like [I-D.ietf-ecrit-specifying-holes] should
be a
Normative rather than Informative reference.
"

[I-D.ietf-ecrit-specifying-holes] specifies one specific way of encoding
holes in PSAP boundaries but the requirement itself is independent of
the chosen approach. 

So, in that sense I would believe there is no normative dependency.
However, if someone does not know what "a hole in a PSAP boundary" means
then they should better read a document and there is only one document
they can read from the IETF ECRIT group that explains this aspect. 

So, what you you suggest me to do? 

Ciao
Hannes