Re: [P2PSIP] Jari Arkko's Discuss on draft-ietf-p2psip-diagnostics-19: (with DISCUSS)

"Songhaibin (A)" <haibin.song@huawei.com> Wed, 06 January 2016 08:27 UTC

Return-Path: <haibin.song@huawei.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED76E1ACCEC; Wed, 6 Jan 2016 00:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 iJ-uDe3C7MjI; Wed, 6 Jan 2016 00:27:53 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EE6C1ACD4C; Wed, 6 Jan 2016 00:27:50 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CGK23886; Wed, 06 Jan 2016 08:27:48 +0000 (GMT)
Received: from LHREML706-CAH.china.huawei.com (10.201.5.182) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Jan 2016 08:27:46 +0000
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 6 Jan 2016 08:27:46 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.252]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0235.001; Wed, 6 Jan 2016 16:26:57 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: Jari Arkko <jari.arkko@piuha.net>, The IESG <iesg@ietf.org>
Thread-Topic: [P2PSIP] Jari Arkko's Discuss on draft-ietf-p2psip-diagnostics-19: (with DISCUSS)
Thread-Index: AQHROJttgUybDgveaES+arOUwnCmH57uQIYw
Date: Wed, 06 Jan 2016 08:26:56 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F65DAC93C@nkgeml513-mbx.china.huawei.com>
References: <20151217072025.29734.77582.idtracker@ietfa.amsl.com>
In-Reply-To: <20151217072025.29734.77582.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.145]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.568CD004.0115, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.252, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: fff2b817d006db24d974353cd93ffeea
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/6K_SvyO0vD2HF9Uqf0oxcrP4kWE>
Cc: "p2psip-chairs@ietf.org" <p2psip-chairs@ietf.org>, "draft-ietf-p2psip-diagnostics@ietf.org" <draft-ietf-p2psip-diagnostics@ietf.org>, "p2psip@ietf.org" <p2psip@ietf.org>, "alexey.melnikov@isode.com" <alexey.melnikov@isode.com>
Subject: Re: [P2PSIP] Jari Arkko's Discuss on draft-ietf-p2psip-diagnostics-19: (with DISCUSS)
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 08:27:58 -0000

Dear Jari,

Thank you. Please see my reply in line.


> -----Original Message-----
> From: P2PSIP [mailto:p2psip-bounces@ietf.org] On Behalf Of Jari Arkko
> Sent: Thursday, December 17, 2015 3:20 PM
> To: The IESG
> Cc: p2psip-chairs@ietf.org; draft-ietf-p2psip-diagnostics@ietf.org;
> p2psip@ietf.org; alexey.melnikov@isode.com
> Subject: [P2PSIP] Jari Arkko's Discuss on draft-ietf-p2psip-diagnostics-19: (with
> DISCUSS)
> 
> Jari Arkko has entered the following ballot position for
> draft-ietf-p2psip-diagnostics-19: Discuss
> 
> 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-p2psip-diagnostics/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Per Alexey's Gen-ART review and my own read, Section 9.1 is inconsistent with
> Section 5.3. The document says earlier that first and last bits are reserved. This
> is not shown in the table at all. What's perhaps causing the confusion is that
> there are special values (all 0s and all 1s) that convey nothing is requested and
> that everything is requested. This does not appear to be the same as having
> two reserved bits. You may want one or the other or both, but as it stands 9.1
> or 5.3 do not seem to be saying the same thing.

In Section 5.3, it says "The dMFlags field described above is a 64 bit field that allows initiator nodes to identify up to 62 items of base information to request in a request message (the first and last flags being reserved)." 62 bits can be used to indicate up to 62 diagnostic Kinds, but dMFlags reserves all "0"s that means nothing is requested, and all "1"s that means everything is requested. But at the same time, the first and last bits cannot be used for other purposes.

> 
> Also, Section 5.3 uses "delimited" when it probably should have said
> "terminated", unless there's more substructure in the SOFTWARE_VERSION
> string than is identified by the text.

It is the language problem and accepted. 

BR,
-Haibin Song

> 
> 
> 
> 
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip