Re: [dispatch] Comments on draft-vanelburg-dispatch-private-network-ind-02

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 09 September 2013 16:18 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A29C21F9AF8 for <dispatch@ietfa.amsl.com>; Mon, 9 Sep 2013 09:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9GPMF1sFDYeR for <dispatch@ietfa.amsl.com>; Mon, 9 Sep 2013 09:18:15 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id B81C311E8116 for <dispatch@ietf.org>; Mon, 9 Sep 2013 09:00:18 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r89G0FfL005743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 9 Sep 2013 11:00:17 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r89G0E3M019174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 9 Sep 2013 18:00:15 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.239]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Mon, 9 Sep 2013 18:00:14 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Mayumi Ohsugi <mayumi.ohsugi@ntt-at.co.jp>, "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: [dispatch] Comments on draft-vanelburg-dispatch-private-network-ind-02
Thread-Index: AQHOpYzy3ziQCFWyLUaMNLfibjb2jpm836qAgAC+T8A=
Date: Mon, 09 Sep 2013 16:00:14 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B09FABF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <201308291521.r7TFLUHc193847@shell01.TheWorld.com> <949EF20990823C4C85C18D59AA11AD8B08B1FC@FR712WXCHMBA11.zeu.alcatel-lucent.com> <201308301426.r7UEQg8q247642@shell01.TheWorld.com> <522D6B23.5080901@ntt-at.co.jp>
In-Reply-To: <522D6B23.5080901@ntt-at.co.jp>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [dispatch] Comments on draft-vanelburg-dispatch-private-network-ind-02
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2013 16:18:21 -0000

The proposed abstract is fine with me.

My main concern was not to make it longer and the proposal meets that concern.

Keith

> -----Original Message-----
> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On
> Behalf Of Mayumi Ohsugi
> Sent: 09 September 2013 07:31
> To: dispatch@ietf.org
> Subject: Re: [dispatch] Comments on draft-vanelburg-dispatch-private-
> network-ind-02
> 
> Hi Dale,
> 
> Thank you for the review and comments on
> draft-vanelburg-dispatch-private-network-ind-02.
> 
> I agree that the abstract needs a statement
> telling what the header means.
> 
> I will correct the abstract as you proposed.
> 
> Thanks,
> Mayumi
> 
> 
> (2013/08/30 23:26), Dale R. Worley wrote:
> >> From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
> >>
> >> I also think the abstract is long enough as it is and your proposed
> >> sentence can be inferred from the text, sufficiently for
> >> bibliographies and so on to identify what the document is about. To
> >> include what you want, what would you delete?
> >
> > I'd say that everything in the abstract can be inferred from the text,
> > but the point of an abstract is that you should be able to read it
> > without reading the text and yet know what the text is about.  I think
> > you've been thinking about PPNI long enough that you don't notice that
> > its purpose isn't obvious to the naive reader.
> >
> > In regard to the size of the abstract, certainly you could omit
> > sentence 4, "The indication also distinguishes traffic from one
> > private network from another private network." as that would be
> > redundant after adding my proposed sentence between sentences 1 and 2.
> > If that isn't sufficient, I would propose removing sentence 2, "The
> > use of ...", as that is pretty much common to all P- headers (and is
> > stated in detail in section 1.2), and isn't as important as describing
> > what the header is *for*.
> >
> > So I propose this as an improved abstract:
> >
> >      This document specifies the SIP P-Private-Network-Indication
> >      P-header used by the 3rd-Generation Partnership Project (3GPP).
> >      The P-Private-Network-Indication indicates that the message is
> >      part of the message traffic of a private network, and identifies
> >      that private network.  A private network indication allows nodes
> >      to treat private network traffic according to a different set of
> >      rules than the set applicable to public network traffic.
> >
> > Dale
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
> >
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch