Re: [P2PSIP] Concepts Draft

"Rosen, Brian" <Brian.Rosen@neustar.biz> Tue, 17 June 2014 17:33 UTC

Return-Path: <Brian.Rosen@neustar.biz>
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 F2D521A00FF for <p2psip@ietfa.amsl.com>; Tue, 17 Jun 2014 10:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level:
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, SPF_PASS=-0.001] autolearn=no
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 wF15EQoC8YcY for <p2psip@ietfa.amsl.com>; Tue, 17 Jun 2014 10:33:08 -0700 (PDT)
Received: from mx0a-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (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 BD6A51A002F for <p2psip@ietf.org>; Tue, 17 Jun 2014 10:33:08 -0700 (PDT)
Received: from pps.filterd (m0049376.ppops.net [127.0.0.1]) by m0049376.ppops.net-0018ba01. (8.14.7/8.14.7) with SMTP id s5HHVX5W018952; Tue, 17 Jun 2014 13:33:07 -0400
Received: from stntexhc10.cis.neustar.com ([156.154.17.216]) by m0049376.ppops.net-0018ba01. with ESMTP id 1mjt5ag02v-5 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 17 Jun 2014 13:33:07 -0400
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.252]) by stntexhc10.cis.neustar.com ([169.254.4.116]) with mapi id 14.03.0158.001; Tue, 17 Jun 2014 13:33:06 -0400
From: "Rosen, Brian" <Brian.Rosen@neustar.biz>
To: David Bryan <dbryan@ethernot.org>
Thread-Topic: [P2PSIP] Concepts Draft
Thread-Index: AQHPilIyipFkUR/LpUm1DuWwzaLPJw==
Date: Tue, 17 Jun 2014 17:33:06 +0000
Message-ID: <C113765E-E794-45FF-8C11-9523E0D2CB67@neustar.biz>
References: <CADqQgCRibXV_xTEmPanFPd=mUH+L2C_WVBixrc5HowKE-K21Gg@mail.gmail.com>
In-Reply-To: <CADqQgCRibXV_xTEmPanFPd=mUH+L2C_WVBixrc5HowKE-K21Gg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.193.24]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <199C29577E081343BC475B49683CFC2C@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7471 signatures=670466
X-Proofpoint-Spam-Reason: safe
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/cvcGjPW1wSvafqgMAigHHvuJl4s
Cc: P2PSIP WG <p2psip@ietf.org>
Subject: Re: [P2PSIP] Concepts Draft
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Jun 2014 17:33:10 -0000

On Jun 13, 2014, at 4:40 PM, David Bryan <dbryan@ethernot.org> wrote:

> I was recently asked to update the concepts draft and discuss the important issues. The pass that has been made is largely around normalizing the text to be compliant with the terminology of RFC 6940, but it certainly will need an additional pass after a few questions to the group: 
> 
> To move this draft forward, there are a few open issues/questions:
> 
>    MAJOR OPEN ISSUE: The initial wording in the high-level description
>    about proving AoR to contact mapping reflects a very long and
>    contentious debate about the role of the protocol, and reflected a
>    pretense that this was an overlay only for P2PSIP.  That is not
>    really true in base anymore (see last paragraph of introduction) and
>    the language has been very much genericized in base.  Should we make
>    this text more abstract and then use AoR->contact mapping as an
>    example of the (original) use?  On a related note, see the last
>    paragraph of the Background section -- do we want to reword this?
> 
> (my thought would be to make the text more generic, and mention that the AoR->contact mapping is the most popular usage…)
Agree

> 
>    OPEN ISSUE: Should we include a section that documents previous
>    decisions made, to preserve the historical debate and prevent past
>    issues from being raised in the future, or simply rely on the mailing
>    list to address these concerns?
> 
> (I don't think we want to do this. Huge (and largely unneeded) can of worms, but it has been in the open issues section for some time and should be at least asked of the list)
No, we don’t need to do this

> 
>    OPEN ISSUE: Should we include the use cases from
>    draft-bryan-p2psip-app-scenarios-00 (now long expired)?  There was
>    some interest in doing so in previous versions, but no conclusion was
>    reached.
> 
> (given the current stage of the group, I would say these aren't likely to be useful anymore, but again, as it is currently listed as an open issue in the draft, need to check)
Nah, I don’t think it is necessary, or even that useful at this point

> 
> The final open issue is do we want to advance the draft? In discussion with the chairs and some folks, it seems the answer is yes, there is useful material and we should push the draft out, but I wanted to discuss. Assuming there is still interest, I'd also welcome any comments on the draft...I'm sure I missed a few spots where it no longer aligns with 6940.
I would like to see this finished.

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