
From nobody Thu Jul  3 12:52:16 2014
Return-Path: <internet-drafts@ietf.org>
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 D10901B2A5A; Thu,  3 Jul 2014 12:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 XcgrTzaFLmNO; Thu,  3 Jul 2014 12:52:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B24241B2A1B; Thu,  3 Jul 2014 12:52:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140703195212.21840.3450.idtracker@ietfa.amsl.com>
Date: Thu, 03 Jul 2014 12:52:12 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/0PpCqT1qZglvq18trY4-c6vGptQ
Cc: p2psip@ietf.org
Subject: [P2PSIP] I-D Action: draft-ietf-p2psip-diagnostics-15.txt
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 03 Jul 2014 19:52:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF.

        Title           : P2P Overlay Diagnostics
        Authors         : Haibin Song
                          Jiang Xingfeng
                          Roni Even
                          David A. Bryan
                          Yi Sun
	Filename        : draft-ietf-p2psip-diagnostics-15.txt
	Pages           : 29
	Date            : 2014-07-03

Abstract:
   This document describes mechanisms for P2P overlay diagnostics.  It
   defines extensions to the RELOAD P2PSIP base protocol to collect
   diagnostic information, and details the protocol specifications for
   these extensions.  Useful diagnostic information for connection and
   node status monitoring is also defined.  The document also describes
   the usage scenarios and provides examples of how these methods are
   used to perform diagnostics in P2PSIP overlay networks.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-p2psip-diagnostics/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-p2psip-diagnostics-15

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-p2psip-diagnostics-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Jul  4 00:54:47 2014
Return-Path: <gonzalo.camarillo@ericsson.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 D359C1A0AC1 for <p2psip@ietfa.amsl.com>; Fri,  4 Jul 2014 00:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 VFCkW3itgbI9 for <p2psip@ietfa.amsl.com>; Fri,  4 Jul 2014 00:54:44 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29D041B2B7D for <p2psip@ietf.org>; Fri,  4 Jul 2014 00:54:43 -0700 (PDT)
X-AuditID: c1b4fb25-f79da6d000004ad3-dd-53b65dc2aed0
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id AB.50.19155.2CD56B35; Fri,  4 Jul 2014 09:54:42 +0200 (CEST)
Received: from [131.160.126.120] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.59) with Microsoft SMTP Server id 14.3.174.1; Fri, 4 Jul 2014 09:54:41 +0200
Message-ID: <53B65DC1.2050805@ericsson.com>
Date: Fri, 4 Jul 2014 10:54:41 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: <p2psip@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmluLIzCtJLcpLzFFi42KZGfG3RvdQ7LZgg5fPZCyW3DzD6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujHMLRArWMFecPJbVwPiCqYuRk0NCwETi66wLLBC2mMSFe+vZ uhi5OIQEjjJKTJ57jBHCWcMocWvCSyCHg4NXQFuie6ErSAOLgIrE2jNTwAaxCVhIbLl1H2yQ qECUxJ1L/awgNq+AoMTJmU/A4iICohKbt18Cq2cWcJV40dDLDDJSWCBAYvKOWBBTQkBcoqcx CKJCT2LK1RZGCFteYvvbOcwgthDQAcuftbBMYBSYhWTBLCQts5C0LGBkXsUoWpxanJSbbmSs l1qUmVxcnJ+nl5dasokRGHoHt/xW3cF4+Y3jIUYBDkYlHl6FWVuDhVgTy4orcw8xSnOwKInz Ljw3L1hIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD49Q91xjYrV1vFp+90f0mtTj13Jt7BdeZ HrjwXzx14T7zTZUsN5tQhy3e9kbN55Wm/1wgM8fh3j7peYZLRKZYJ1vwF/7w+5u4r8azO2Ex S25ehnbAq8i1XYXPrk4UVNpvXHHjot0/sd2lgUveT3x08JYfV9kah6iN1/J38x5zFgg9zBh6 OkY0U4mlOCPRUIu5qDgRAIlQjbgeAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/tJQFgMjviRIn3HsjLvxZB1VHBwc
Subject: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
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: Fri, 04 Jul 2014 07:54:46 -0000

Folks,

we need to decide the IANA registration policy to register new services
in the draft below:

http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#section-10.4

Out of the well-known IANA policies below, would Specification Required
(which includes a designated expert who will review new registrations)
be OK with the group?

http://tools.ietf.org/html/rfc5226#section-4.1

Cheers,

Gonzalo


From nobody Mon Jul  7 08:15:21 2014
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 3171D1A0166 for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 08:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Level: 
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 6-k3zaQdQN7c for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 08:15:18 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0b-0018ba01.pphosted.com [67.231.157.90]) (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 B54501A0162 for <p2psip@ietf.org>; Mon,  7 Jul 2014 08:15:18 -0700 (PDT)
Received: from pps.filterd (m0049367.ppops.net [127.0.0.1]) by m0049367.ppops.net-0018ba01. (8.14.7/8.14.7) with SMTP id s67F7xKW007732; Mon, 7 Jul 2014 11:15:15 -0400
Received: from stntexhc11.cis.neustar.com ([156.154.17.216]) by m0049367.ppops.net-0018ba01. with ESMTP id 1mywv000pj-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 07 Jul 2014 11:15:15 -0400
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.252]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.03.0158.001; Mon, 7 Jul 2014 11:15:14 -0400
From: "Rosen, Brian" <Brian.Rosen@neustar.biz>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Thread-Topic: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
Thread-Index: AQHPmfZA6TI7EMBUjkWX2onzS6JExA==
Date: Mon, 7 Jul 2014 15:15:13 +0000
Message-ID: <7C80BF6A-A600-42F3-9425-2659D3C1CFF5@neustar.biz>
References: <53B65DC1.2050805@ericsson.com>
In-Reply-To: <53B65DC1.2050805@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.192.29]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F5A610C4B838E24FB60F6F46E6783EE1@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7491 signatures=670477
X-Proofpoint-Spam-Reason: safe
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/Otj6dgey234j-76l7BgAAmOy7aU
Cc: "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
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: Mon, 07 Jul 2014 15:15:20 -0000

Yeah, that seems to be appropriate to me.

Brian

On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.c=
om> wrote:

> Folks,
>=20
> we need to decide the IANA registration policy to register new services
> in the draft below:
>=20
> http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#section=
-10.4
>=20
> Out of the well-known IANA policies below, would Specification Required
> (which includes a designated expert who will review new registrations)
> be OK with the group?
>=20
> http://tools.ietf.org/html/rfc5226#section-4.1
>=20
> Cheers,
>=20
> Gonzalo
>=20
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip


From nobody Mon Jul  7 13:06:18 2014
Return-Path: <dbryan@ethernot.org>
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 973071B28B4 for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 13:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.198
X-Spam-Level: 
X-Spam-Status: No, score=-1.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] 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 Yi1k7Vn5cu7A for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 13:06:14 -0700 (PDT)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79D881A0A88 for <p2psip@ietf.org>; Mon,  7 Jul 2014 13:06:14 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id n12so3121275wgh.13 for <p2psip@ietf.org>; Mon, 07 Jul 2014 13:06:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=loJ93q3HHBj0t+Cses3q4lBiVb08uWnmxkWKD9J4YKw=; b=XXddZVOqfCikGKb6F7wfOOXErJV+AYpCpkFBOzq1GNNfqcKouuNIYzRocD3JLAIONr adbUimQWZKmt1u6kUWAcud6q3lJcw6YxXg+N1WK6y06/e90EhKxfkaDRgL9UWgNbbcON cGt3zbEtl0ihXOZkzm1+EtseciEGczVTP7LZglr4b3TDfvRxAqUofSwiR9ll2pm1comh VgdPlehH2p4DnrwIQXAYZOAlIQpTvGyr0McbtTYdxtYCyt+f0mcyGgu9GiSqTrsFgkVC 3Nj/YhK1ODfVUNU6rdukNv8bMD/Y1vEIL+8kKPGrXgL02HdiCvHCdDYmZ8xksT5HzQ/u 7lvQ==
X-Gm-Message-State: ALoCoQkGTDxOe5p3w8rF9/pdp2zREKP3pvnYAKEU5XkylaNUs0dJnh9xIJVnmwGzMVyE2d4E9zTq
MIME-Version: 1.0
X-Received: by 10.180.212.68 with SMTP id ni4mr39211862wic.64.1404763573016; Mon, 07 Jul 2014 13:06:13 -0700 (PDT)
Received: by 10.180.92.9 with HTTP; Mon, 7 Jul 2014 13:06:12 -0700 (PDT)
X-Originating-IP: [70.116.37.150]
In-Reply-To: <7C80BF6A-A600-42F3-9425-2659D3C1CFF5@neustar.biz>
References: <53B65DC1.2050805@ericsson.com> <7C80BF6A-A600-42F3-9425-2659D3C1CFF5@neustar.biz>
Date: Mon, 7 Jul 2014 15:06:12 -0500
Message-ID: <CADqQgCQKzCHbFR8bS1SL+8R8zQ7=b=PyYACNv6R0-Zmdr3ZTTQ@mail.gmail.com>
From: David Bryan <dbryan@ethernot.org>
To: "Rosen, Brian" <Brian.Rosen@neustar.biz>
Content-Type: multipart/alternative; boundary=001a11c3570cc377f104fda001cc
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/pCpfecMW_dStWEZ-yrkAhBAq4eE
Cc: "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
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: Mon, 07 Jul 2014 20:06:17 -0000

--001a11c3570cc377f104fda001cc
Content-Type: text/plain; charset=UTF-8

A bit curious...why Specification Required vs. RFC Required? Do you
envision some other formal, but non-IETF document (other standards group,
perhaps) being a valid path?

Certainly no objection. The distinction between the two is just a bit
confusing to me.


On Mon, Jul 7, 2014 at 10:15 AM, Rosen, Brian <Brian.Rosen@neustar.biz>
wrote:

> Yeah, that seems to be appropriate to me.
>
> Brian
>
> On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo <
> Gonzalo.Camarillo@ericsson.com> wrote:
>
> > Folks,
> >
> > we need to decide the IANA registration policy to register new services
> > in the draft below:
> >
> >
> http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#section-10.4
> >
> > Out of the well-known IANA policies below, would Specification Required
> > (which includes a designated expert who will review new registrations)
> > be OK with the group?
> >
> > http://tools.ietf.org/html/rfc5226#section-4.1
> >
> > Cheers,
> >
> > Gonzalo
> >
> > _______________________________________________
> > P2PSIP mailing list
> > P2PSIP@ietf.org
> > https://www.ietf.org/mailman/listinfo/p2psip
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org
> https://www.ietf.org/mailman/listinfo/p2psip
>

--001a11c3570cc377f104fda001cc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">A bit curious...why Specification Required vs. RFC Require=
d? Do you envision some other formal, but non-IETF document (other standard=
s group, perhaps) being a valid path?<div><br></div><div>Certainly no objec=
tion. The distinction between the two is just a bit confusing to me.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
 Jul 7, 2014 at 10:15 AM, Rosen, Brian <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:Brian.Rosen@neustar.biz" target=3D"_blank">Brian.Rosen@neustar.biz</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Yeah, that seems to be appropriate to me.<br=
>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Brian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo &lt;<a href=3D"mailto:Gonzalo=
.Camarillo@ericsson.com">Gonzalo.Camarillo@ericsson.com</a>&gt; wrote:<br>
<br>
&gt; Folks,<br>
&gt;<br>
&gt; we need to decide the IANA registration policy to register new service=
s<br>
&gt; in the draft below:<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-p2psip-service-discov=
ery-13#section-10.4" target=3D"_blank">http://tools.ietf.org/html/draft-iet=
f-p2psip-service-discovery-13#section-10.4</a><br>
&gt;<br>
&gt; Out of the well-known IANA policies below, would Specification Require=
d<br>
&gt; (which includes a designated expert who will review new registrations)=
<br>
&gt; be OK with the group?<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/rfc5226#section-4.1" target=3D"_=
blank">http://tools.ietf.org/html/rfc5226#section-4.1</a><br>
&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; Gonzalo<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; P2PSIP mailing list<br>
&gt; <a href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/p2psip" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/p2psip</a><br>
<br>
_______________________________________________<br>
P2PSIP mailing list<br>
<a href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/p2psip" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/p2psip</a><br>
</div></div></blockquote></div><br></div>

--001a11c3570cc377f104fda001cc--


From nobody Mon Jul  7 13:15:52 2014
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 4183E1B28C1 for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 13:15:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.566
X-Spam-Level: 
X-Spam-Status: No, score=-1.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 nrWP3FOXhu7Y for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 13:15:50 -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 3FBD61B28D3 for <p2psip@ietf.org>; Mon,  7 Jul 2014 13:15:47 -0700 (PDT)
Received: from pps.filterd (m0049402.ppops.net [127.0.0.1]) by m0049402.ppops.net-0018ba01. (8.14.7/8.14.7) with SMTP id s67KEf70019437; Mon, 7 Jul 2014 16:15:42 -0400
Received: from stntexhc10.cis.neustar.com ([156.154.17.216]) by m0049402.ppops.net-0018ba01. with ESMTP id 1my57thmur-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 07 Jul 2014 16:15:42 -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; Mon, 7 Jul 2014 16:15:41 -0400
From: "Rosen, Brian" <Brian.Rosen@neustar.biz>
To: David Bryan <dbryan@ethernot.org>
Thread-Topic: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
Thread-Index: AQHPmfZA6TI7EMBUjkWX2onzS6JExJuVTO4A//+/lYA=
Date: Mon, 7 Jul 2014 20:15:40 +0000
Message-ID: <CFE077DF.7038C%brian.rosen@neustar.biz>
References: <53B65DC1.2050805@ericsson.com> <7C80BF6A-A600-42F3-9425-2659D3C1CFF5@neustar.biz> <CADqQgCQKzCHbFR8bS1SL+8R8zQ7=b=PyYACNv6R0-Zmdr3ZTTQ@mail.gmail.com>
In-Reply-To: <CADqQgCQKzCHbFR8bS1SL+8R8zQ7=b=PyYACNv6R0-Zmdr3ZTTQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.33.192.29]
Content-Type: multipart/alternative; boundary="_000_CFE077DF7038Cbrianrosenneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7492 signatures=670477
X-Proofpoint-Spam-Reason: safe
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/n77ehM_mNMh3NXthuYW3Rp0rGE0
Cc: "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
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: Mon, 07 Jul 2014 20:15:51 -0000

--_000_CFE077DF7038Cbrianrosenneustarbiz_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Experience suggest that some services can be created by some independent pa=
rty, and often memorialized with a informational document.  But, let=92s sa=
y someone like OMS decides to do one =96 no problem.

Brian

From: David Bryan <dbryan@ethernot.org<mailto:dbryan@ethernot.org>>
Date: Monday, July 7, 2014 at 1:06 PM
To: Brian Rosen <brian.rosen@neustar.biz<mailto:brian.rosen@neustar.biz>>
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com<mailto:Gonzalo.Camari=
llo@ericsson.com>>, "p2psip@ietf.org<mailto:p2psip@ietf.org>" <p2psip@ietf.=
org<mailto:p2psip@ietf.org>>
Subject: Re: [P2PSIP] Registration policy for services in draft-ietf-p2psip=
-service-discovery

A bit curious...why Specification Required vs. RFC Required? Do you envisio=
n some other formal, but non-IETF document (other standards group, perhaps)=
 being a valid path?

Certainly no objection. The distinction between the two is just a bit confu=
sing to me.


On Mon, Jul 7, 2014 at 10:15 AM, Rosen, Brian <Brian.Rosen@neustar.biz<mail=
to:Brian.Rosen@neustar.biz>> wrote:
Yeah, that seems to be appropriate to me.

Brian

On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.c=
om<mailto:Gonzalo.Camarillo@ericsson.com>> wrote:

> Folks,
>
> we need to decide the IANA registration policy to register new services
> in the draft below:
>
> http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#section=
-10.4
>
> Out of the well-known IANA policies below, would Specification Required
> (which includes a designated expert who will review new registrations)
> be OK with the group?
>
> http://tools.ietf.org/html/rfc5226#section-4.1
>
> Cheers,
>
> Gonzalo
>
> _______________________________________________
> P2PSIP mailing list
> P2PSIP@ietf.org<mailto:P2PSIP@ietf.org>
> https://www.ietf.org/mailman/listinfo/p2psip

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


--_000_CFE077DF7038Cbrianrosenneustarbiz_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <3629E373ED0E414CA7BC0B5E6D3DD2AA@neustar.biz>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Experience suggest that some services can be created by some independe=
nt party, and often memorialized with a informational document. &nbsp;But, =
let=92s say someone like OMS decides to do one =96 no problem.</div>
<div><br>
</div>
<div>Brian</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>David Bryan &lt;<a href=3D"ma=
ilto:dbryan@ethernot.org">dbryan@ethernot.org</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, July 7, 2014 at 1:06 =
PM<br>
<span style=3D"font-weight:bold">To: </span>Brian Rosen &lt;<a href=3D"mail=
to:brian.rosen@neustar.biz">brian.rosen@neustar.biz</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Gonzalo Camarillo &lt;<a href=
=3D"mailto:Gonzalo.Camarillo@ericsson.com">Gonzalo.Camarillo@ericsson.com</=
a>&gt;, &quot;<a href=3D"mailto:p2psip@ietf.org">p2psip@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:p2psip@ietf.org">p2psip@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [P2PSIP] Registration =
policy for services in draft-ietf-p2psip-service-discovery<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">A bit curious...why Specification Required vs. RFC Require=
d? Do you envision some other formal, but non-IETF document (other standard=
s group, perhaps) being a valid path?
<div><br>
</div>
<div>Certainly no objection. The distinction between the two is just a bit =
confusing to me.</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Mon, Jul 7, 2014 at 10:15 AM, Rosen, Brian <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:Brian.Rosen@neustar.biz" target=3D"_blank">Brian.Rose=
n@neustar.biz</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yeah, that seems to be appropriate to me.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Brian<br>
</font></span>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo &lt;<a href=3D"mailto:Gonzalo=
.Camarillo@ericsson.com">Gonzalo.Camarillo@ericsson.com</a>&gt; wrote:<br>
<br>
&gt; Folks,<br>
&gt;<br>
&gt; we need to decide the IANA registration policy to register new service=
s<br>
&gt; in the draft below:<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-p2psip-service-discov=
ery-13#section-10.4" target=3D"_blank">
http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#section-1=
0.4</a><br>
&gt;<br>
&gt; Out of the well-known IANA policies below, would Specification Require=
d<br>
&gt; (which includes a designated expert who will review new registrations)=
<br>
&gt; be OK with the group?<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/rfc5226#section-4.1" target=3D"_=
blank">http://tools.ietf.org/html/rfc5226#section-4.1</a><br>
&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; Gonzalo<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; P2PSIP mailing list<br>
&gt; <a href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/p2psip" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/p2psip</a><br>
<br>
_______________________________________________<br>
P2PSIP mailing list<br>
<a href=3D"mailto:P2PSIP@ietf.org">P2PSIP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/p2psip" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/p2psip</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CFE077DF7038Cbrianrosenneustarbiz_--


From nobody Mon Jul  7 13:17:04 2014
Return-Path: <dbryan@ethernot.org>
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 ABBE31A0A88 for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 13:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.198
X-Spam-Level: 
X-Spam-Status: No, score=-1.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] 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 GteohIjTDRxt for <p2psip@ietfa.amsl.com>; Mon,  7 Jul 2014 13:17:01 -0700 (PDT)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A58691A0515 for <p2psip@ietf.org>; Mon,  7 Jul 2014 13:17:00 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id hi2so7355874wib.13 for <p2psip@ietf.org>; Mon, 07 Jul 2014 13:16:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=zjCx6U+HKOoLrTUDbkjr2YdCVICGvDEVw9s8ncHZL0g=; b=MmPYtgmpFGY5YR2YBk/krgeNkLb4tpCw/t6WK67ZbJTg//ldew5hiZWKZkFVTm6A4W n8xeWTV2JziL5C56ihwHH+VdYIe65wBR2aSpS2mxreRzmqOD4Wk2Y0txhs4OwTFVl+11 3l8BBSZiftcwsRKup2PHCmjXL5R7SGW7rDUw+Z/fKRR7jmv6LXz94y09YhoFe+nto6zk +GtZLtLfCofDoy9R/qqn2vfPEV9uNM4o2VmHuNMo4dc2LTkP3BIul4otZGZ3ADDWKzwp HdgekhqVZrp6QtKBcfGS+T6j0CZCN4J4eSKRliOIazWiZhI9pmdLYRTs1QR67rQUN1PB wRbQ==
X-Gm-Message-State: ALoCoQm/VktcSb1lRcn8OkZ92Zpt0MTQBkm3T1q8GFEUggXq+NBnEyvn13z75D3S//I4mjv0g/q8
MIME-Version: 1.0
X-Received: by 10.180.10.168 with SMTP id j8mr79504418wib.73.1404764219296; Mon, 07 Jul 2014 13:16:59 -0700 (PDT)
Received: by 10.180.92.9 with HTTP; Mon, 7 Jul 2014 13:16:59 -0700 (PDT)
X-Originating-IP: [70.116.37.150]
In-Reply-To: <CFE077DF.7038C%brian.rosen@neustar.biz>
References: <53B65DC1.2050805@ericsson.com> <7C80BF6A-A600-42F3-9425-2659D3C1CFF5@neustar.biz> <CADqQgCQKzCHbFR8bS1SL+8R8zQ7=b=PyYACNv6R0-Zmdr3ZTTQ@mail.gmail.com> <CFE077DF.7038C%brian.rosen@neustar.biz>
Date: Mon, 7 Jul 2014 15:16:59 -0500
Message-ID: <CADqQgCSi71E+zo7Kt7fjxqKXEOY3UASjiJ=LJ+cL_4u_yEHngA@mail.gmail.com>
From: David Bryan <dbryan@ethernot.org>
To: "Rosen, Brian" <Brian.Rosen@neustar.biz>
Content-Type: multipart/alternative; boundary=001a11c2591848e36804fda028a9
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/3QylFqc5JiKGsSFr_tIUHIUXGpg
Cc: "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] Registration policy for services in draft-ietf-p2psip-service-discovery
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: Mon, 07 Jul 2014 20:17:03 -0000

--001a11c2591848e36804fda028a9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Makes sense. Thanks.


On Mon, Jul 7, 2014 at 3:15 PM, Rosen, Brian <Brian.Rosen@neustar.biz>
wrote:

>  Experience suggest that some services can be created by some independent
> party, and often memorialized with a informational document.  But, let=E2=
=80=99s
> say someone like OMS decides to do one =E2=80=93 no problem.
>
>  Brian
>
>   From: David Bryan <dbryan@ethernot.org>
> Date: Monday, July 7, 2014 at 1:06 PM
> To: Brian Rosen <brian.rosen@neustar.biz>
> Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "p2psip@ietf.org"
> <p2psip@ietf.org>
> Subject: Re: [P2PSIP] Registration policy for services in
> draft-ietf-p2psip-service-discovery
>
>   A bit curious...why Specification Required vs. RFC Required? Do you
> envision some other formal, but non-IETF document (other standards group,
> perhaps) being a valid path?
>
>  Certainly no objection. The distinction between the two is just a bit
> confusing to me.
>
>
> On Mon, Jul 7, 2014 at 10:15 AM, Rosen, Brian <Brian.Rosen@neustar.biz>
> wrote:
>
>> Yeah, that seems to be appropriate to me.
>>
>> Brian
>>
>> On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo <
>> Gonzalo.Camarillo@ericsson.com> wrote:
>>
>> > Folks,
>> >
>> > we need to decide the IANA registration policy to register new service=
s
>> > in the draft below:
>> >
>> >
>> http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#sectio=
n-10.4
>> >
>> > Out of the well-known IANA policies below, would Specification Require=
d
>> > (which includes a designated expert who will review new registrations)
>> > be OK with the group?
>> >
>> > http://tools.ietf.org/html/rfc5226#section-4.1
>> >
>> > Cheers,
>> >
>> > Gonzalo
>> >
>> > _______________________________________________
>> > P2PSIP mailing list
>> > P2PSIP@ietf.org
>> > https://www.ietf.org/mailman/listinfo/p2psip
>>
>> _______________________________________________
>> P2PSIP mailing list
>> P2PSIP@ietf.org
>> https://www.ietf.org/mailman/listinfo/p2psip
>>
>
>

--001a11c2591848e36804fda028a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Makes sense. Thanks.</div><div class=3D"gmail_extra"><br><=
br><div class=3D"gmail_quote">On Mon, Jul 7, 2014 at 3:15 PM, Rosen, Brian =
<span dir=3D"ltr">&lt;<a href=3D"mailto:Brian.Rosen@neustar.biz" target=3D"=
_blank">Brian.Rosen@neustar.biz</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Experience suggest that some services can be created by some independe=
nt party, and often memorialized with a informational document. =C2=A0But, =
let=E2=80=99s say someone like OMS decides to do one =E2=80=93 no problem.<=
/div>
<div><br>
</div>
<div>Brian</div>
<div><br>
</div>
<span>
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">

<span style=3D"font-weight:bold">From: </span>David Bryan &lt;<a href=3D"ma=
ilto:dbryan@ethernot.org" target=3D"_blank">dbryan@ethernot.org</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, July 7, 2014 at 1:06 =
PM<br>
<span style=3D"font-weight:bold">To: </span>Brian Rosen &lt;<a href=3D"mail=
to:brian.rosen@neustar.biz" target=3D"_blank">brian.rosen@neustar.biz</a>&g=
t;<br>
<span style=3D"font-weight:bold">Cc: </span>Gonzalo Camarillo &lt;<a href=
=3D"mailto:Gonzalo.Camarillo@ericsson.com" target=3D"_blank">Gonzalo.Camari=
llo@ericsson.com</a>&gt;, &quot;<a href=3D"mailto:p2psip@ietf.org" target=
=3D"_blank">p2psip@ietf.org</a>&quot; &lt;<a href=3D"mailto:p2psip@ietf.org=
" target=3D"_blank">p2psip@ietf.org</a>&gt;<br>

<span style=3D"font-weight:bold">Subject: </span>Re: [P2PSIP] Registration =
policy for services in draft-ietf-p2psip-service-discovery<br>
</div><div><div class=3D"h5">
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">A bit curious...why Specification Required vs. RFC Require=
d? Do you envision some other formal, but non-IETF document (other standard=
s group, perhaps) being a valid path?
<div><br>
</div>
<div>Certainly no objection. The distinction between the two is just a bit =
confusing to me.</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Mon, Jul 7, 2014 at 10:15 AM, Rosen, Brian <s=
pan dir=3D"ltr">
&lt;<a href=3D"mailto:Brian.Rosen@neustar.biz" target=3D"_blank">Brian.Rose=
n@neustar.biz</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yeah, that seems to be appropriate to me.<br>
<span><font color=3D"#888888"><br>
Brian<br>
</font></span>
<div>
<div><br>
On Jul 4, 2014, at 3:54 AM, Gonzalo Camarillo &lt;<a href=3D"mailto:Gonzalo=
.Camarillo@ericsson.com" target=3D"_blank">Gonzalo.Camarillo@ericsson.com</=
a>&gt; wrote:<br>
<br>
&gt; Folks,<br>
&gt;<br>
&gt; we need to decide the IANA registration policy to register new service=
s<br>
&gt; in the draft below:<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-p2psip-service-discov=
ery-13#section-10.4" target=3D"_blank">
http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-13#section-1=
0.4</a><br>
&gt;<br>
&gt; Out of the well-known IANA policies below, would Specification Require=
d<br>
&gt; (which includes a designated expert who will review new registrations)=
<br>
&gt; be OK with the group?<br>
&gt;<br>
&gt; <a href=3D"http://tools.ietf.org/html/rfc5226#section-4.1" target=3D"_=
blank">http://tools.ietf.org/html/rfc5226#section-4.1</a><br>
&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; Gonzalo<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; P2PSIP mailing list<br>
&gt; <a href=3D"mailto:P2PSIP@ietf.org" target=3D"_blank">P2PSIP@ietf.org</=
a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/p2psip" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/p2psip</a><br>
<br>
_______________________________________________<br>
P2PSIP mailing list<br>
<a href=3D"mailto:P2PSIP@ietf.org" target=3D"_blank">P2PSIP@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/p2psip" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/p2psip</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div></div></span>
</div>

</blockquote></div><br></div>

--001a11c2591848e36804fda028a9--


From nobody Mon Jul 21 11:28:04 2014
Return-Path: <gonzalo.camarillo@ericsson.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 95DB61A01E6 for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 11:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 dxUOTkVJQ3MR for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 11:28:00 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 707541A010A for <p2psip@ietf.org>; Mon, 21 Jul 2014 11:27:59 -0700 (PDT)
X-AuditID: c1b4fb2d-f798a6d000000e9b-d7-53cd5bad7fb2
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 1D.ED.03739.DAB5DC35; Mon, 21 Jul 2014 20:27:57 +0200 (CEST)
Received: from [131.160.126.92] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.26) with Microsoft SMTP Server id 14.3.174.1; Mon, 21 Jul 2014 20:27:56 +0200
Message-ID: <53CD5BAC.3080500@ericsson.com>
Date: Mon, 21 Jul 2014 14:27:56 -0400
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: <p2psip@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUyM+Jvje7a6LPBBm3TDC2mn/nLaLHk5hlG ByaPL09eMnksWfKTKYApissmJTUnsyy1SN8ugSujq2kyU8F5pooHzw+yNzD2M3UxcnJICJhI 7P9/gR3CFpO4cG89WxcjF4eQwFFGib9NF5ggnDWMEn+uT2UGqeIV0Jb4dvIZI4jNIqAqMa+p nwXEZhOwkNhy6z6YLSoQJXHnUj8rRL2gxMmZT8DiIgKiEpu3XwLbzAzUe/95M9A2Dg5hASOJ Z+9tQEwJAXGJnsYgiAo9iSlXWxghbHmJ7W/ngF0gBHTB8mctLBMYBWYhWTALScssJC0LGJlX MYoWpxYX56YbGeulFmUmFxfn5+nlpZZsYgQG5cEtv3V3MK5+7XiIUYCDUYmHVyH0bLAQa2JZ cWXuIUZpDhYlcd5F5+YFCwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamAMmXTUolpafKKqQMfO lRcPSe1b/85Mzo1dMSGhwTTzwZ2NwheDj606m794btUDq00tsn739m7ktlyXv8nmSeL57xvr 7nzXvJd85Io4692mxUrn95vKP2U9Hfb5ITuX98WMEje+p01+u7fKNkSue6ycwS3/W4fZI870 KoNIVvLdB3NXL5tR/WiNEktxRqKhFnNRcSIAeiJ6pisCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/sCAoPseHkZCDP_BTsubq51S1Aa0
Subject: [P2PSIP] Revision of draft-ietf-p2psip-self-tuning
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: Mon, 21 Jul 2014 18:28:01 -0000

Hi,

we have revised the draft below in order to address IESG comments. At
this point, the draft is ready to be approved from an IESG's perspective.

http://tools.ietf.org/rfcdiff?url2=draft-ietf-p2psip-self-tuning-15.txt

Please, have a look at the new revision. Alissa intends to approve it
shortly.

Thanks,

Gonzalo


From nobody Mon Jul 21 11:41:16 2014
Return-Path: <internet-drafts@ietf.org>
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 40F611A0360; Mon, 21 Jul 2014 11:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 cOc4c9ygj55m; Mon, 21 Jul 2014 11:41:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E93421A0345; Mon, 21 Jul 2014 11:41:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140721184103.22740.54923.idtracker@ietfa.amsl.com>
Date: Mon, 21 Jul 2014 11:41:03 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/ytI37ODBYdevKByRrgxQVB4_W6Q
Cc: p2psip@ietf.org
Subject: [P2PSIP] I-D Action: draft-ietf-p2psip-sip-13.txt
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 21 Jul 2014 18:41:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF.

        Title           : A SIP Usage for RELOAD
        Authors         : Cullen Jennings
                          Bruce B. Lowekamp
                          Eric Rescorla
                          Salman A. Baset
                          Henning Schulzrinne
                          Thomas C. Schmidt
	Filename        : draft-ietf-p2psip-sip-13.txt
	Pages           : 20
	Date            : 2014-07-21

Abstract:
   This document defines a SIP Usage for REsource LOcation And Discovery
   (RELOAD).  The SIP Usage provides the functionality of a SIP proxy or
   registrar in a fully-distributed system and includes a lookup service
   for Address of Records (AORs) stored in the overlay.  It also defines
   Globally Routable User Agent Uris (GRUUs) that allow the
   registrations to map an AOR to a specific node reachable through the
   overlay.  After such initial contact of a peer, the AppAttach method
   is used to establish a direct connection between nodes through which
   SIP messages are exchanged.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-p2psip-sip/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-p2psip-sip-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-p2psip-sip-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Jul 21 11:48:00 2014
Return-Path: <schmidt@informatik.haw-hamburg.de>
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 E9BD21A011C for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 11:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.25
X-Spam-Level: 
X-Spam-Status: No, score=-1.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001] 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 N4zYuQgHwjAQ for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 11:47:51 -0700 (PDT)
Received: from mail1.rz.htw-berlin.de (mail1.rz.htw-berlin.de [141.45.10.101]) (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 45CD51A015F for <p2psip@ietf.org>; Mon, 21 Jul 2014 11:47:49 -0700 (PDT)
Envelope-to: p2psip@ietf.org
Received: from dhcp-a74b.meeting.ietf.org ([31.133.167.75]) by mail1.rz.htw-berlin.de with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1X9Ick-000D4e-I4; Mon, 21 Jul 2014 20:47:46 +0200
Message-ID: <53CD6050.2030206@informatik.haw-hamburg.de>
Date: Mon, 21 Jul 2014 14:47:44 -0400
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>, =?UTF-8?B?Q2FybG9zIEplc8O6cyBCZXJuYXI=?= =?UTF-8?B?ZG9zIENhbm8=?= <cjbc@it.uc3m.es>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com>
In-Reply-To: <20140721184000.22310.54252.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140721184000.22310.54252.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: p2psip@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/qGXJr6p5v4YFZ9V34gjOi0z-BQg
Cc: p2psip@ietf.org
Subject: [P2PSIP] Fwd: Confirm submission of I-D draft-ietf-p2psip-sip
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: Mon, 21 Jul 2014 18:47:53 -0000

Hi Chairs,

I wonder about moving this document?

It has been ready in so loop since a long time ... same goes for 
draft-ietf-p2psip-share-03.

How are plans?

Thanks,

Thomas

-------- Original Message --------
Subject: Confirm submission of I-D draft-ietf-p2psip-sip
Date: Mon, 21 Jul 2014 11:40:00 -0700
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp 
<bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset 
<salman@cs.columbia.edu>, Henning Schulzrinne <hgs@cs.columbia.edu>, 
Thomas Schmidt <Schmidt@informatik.haw-hamburg.de>


Hi,

The IETF datatracker draft submission service has received your draft
draft-ietf-p2psip-sip-13, and requires a
confirmation step in order to be able to complete the posting of
the draft.

Please follow this link to the page where you can confirm the posting:

http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d172f5975b09068/


Best regards,

	The IETF Secretariat
	through the draft submission service





From nobody Mon Jul 21 12:26:17 2014
Return-Path: <br@brianrosen.net>
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 4400E1A01F3 for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 12:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level: 
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] 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 wNW_rrnMS6Bp for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 12:26:14 -0700 (PDT)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2810F1A0142 for <p2psip@ietf.org>; Mon, 21 Jul 2014 12:26:14 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b13so6847497wgh.34 for <p2psip@ietf.org>; Mon, 21 Jul 2014 12:26:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=IadvUqUhHVG304gZazDj4mRdxmNonqWi52NwGQC5G5o=; b=PXzFqec/QAEG58Zc3gK9/IWgL0YTTzmBuzLmBODFj7LbNybmQ/3Exf6aivQjiZdQ9L T3/l8h/zdO6ZVMQo8TJ62SDDGXaousiewPQkE+OPMHx4f3H2eSZYdLtdWp+ch3d/oFfY 0koDH12RVHMimNkUXPMhQIucJTfWoetccnrTOLz/5IWXb2sw9u9U/hk86lByn64S1MGR 9wJ6svyNSbfH5OXLP417g0yS0uFawGtB10iwSTySjKU/qga+XDRJObyUhQq/rbEMvMeR QiYokaM9SwxGBa6RmntkyH+F/KdWZ5ZLPMQH58OTP5DxUQuO37FXOVK1m9JUX7FuJ9kV E+Gw==
X-Gm-Message-State: ALoCoQmorda98Db4LJqEfysovd4+M2GT4ogvcPmDnR31djhCMHLC/59RcHW7Dto16YWSMD29l9RL
X-Received: by 10.194.9.198 with SMTP id c6mr17379303wjb.131.1405970772238; Mon, 21 Jul 2014 12:26:12 -0700 (PDT)
Received: from dhcp-b334.meeting.ietf.org (dhcp-b334.meeting.ietf.org. [31.133.179.52]) by mx.google.com with ESMTPSA id ft6sm11256099wic.0.2014.07.21.12.26.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jul 2014 12:26:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <53CD6050.2030206@informatik.haw-hamburg.de>
Date: Mon, 21 Jul 2014 15:26:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de>
To: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/tgX0r-_9q0D3pkqO5ra4b65lGNw
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] Confirm submission of I-D draft-ietf-p2psip-sip
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: Mon, 21 Jul 2014 19:26:16 -0000

If there is anyone with energy to finish this document, I think it would =
be good to do so.  But unless someone steps up to the task of getting it =
done and through the process, I think we ought to abandon it.

Brian

On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt =
<schmidt@informatik.haw-hamburg.de> wrote:

> Hi Chairs,
>=20
> I wonder about moving this document?
>=20
> It has been ready in so loop since a long time ... same goes for =
draft-ietf-p2psip-share-03.
>=20
> How are plans?
>=20
> Thanks,
>=20
> Thomas
>=20
> -------- Original Message --------
> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
> Date: Mon, 21 Jul 2014 11:40:00 -0700
> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp =
<bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset =
<salman@cs.columbia.edu>, Henning Schulzrinne <hgs@cs.columbia.edu>, =
Thomas Schmidt <Schmidt@informatik.haw-hamburg.de>
>=20
>=20
> Hi,
>=20
> The IETF datatracker draft submission service has received your draft
> draft-ietf-p2psip-sip-13, and requires a
> confirmation step in order to be able to complete the posting of
> the draft.
>=20
> Please follow this link to the page where you can confirm the posting:
>=20
> =
http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d=
172f5975b09068/
>=20
>=20
> Best regards,
>=20
> 	The IETF Secretariat
> 	through the draft submission service
>=20
>=20
>=20
>=20


From nobody Mon Jul 21 12:32:32 2014
Return-Path: <schmidt@informatik.haw-hamburg.de>
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 04B561A032A for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 12:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001] 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 9cu8Hiv0ROkP for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 12:32:29 -0700 (PDT)
Received: from mail1.rz.htw-berlin.de (mail1.rz.htw-berlin.de [141.45.10.101]) (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 695F31A00AB for <p2psip@ietf.org>; Mon, 21 Jul 2014 12:32:29 -0700 (PDT)
Envelope-to: p2psip@ietf.org
Received: from dhcp-a74b.meeting.ietf.org ([31.133.167.75]) by mail1.rz.htw-berlin.de with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1X9JJy-000Ep6-Cv; Mon, 21 Jul 2014 21:32:26 +0200
Message-ID: <53CD6AC6.4040908@informatik.haw-hamburg.de>
Date: Mon, 21 Jul 2014 15:32:22 -0400
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net>
In-Reply-To: <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: p2psip@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/c4myZu1IC_t0IJZ-ra9IKEsGquQ
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
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: Mon, 21 Jul 2014 19:32:31 -0000

Hi Brian,

from my understanding, the document is finished in the WG. I guess it 
mainly needs a shepherd for going on, or what do you refer to?

Thanks,

Thomas



On 21.07.2014 15:26, Brian Rosen wrote:
> If there is anyone with energy to finish this document, I think it would be good to do so.  But unless someone steps up to the task of getting it done and through the process, I think we ought to abandon it.
>
> Brian
>
> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de> wrote:
>
>> Hi Chairs,
>>
>> I wonder about moving this document?
>>
>> It has been ready in so loop since a long time ... same goes for draft-ietf-p2psip-share-03.
>>
>> How are plans?
>>
>> Thanks,
>>
>> Thomas
>>
>> -------- Original Message --------
>> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
>> Date: Mon, 21 Jul 2014 11:40:00 -0700
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp <bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset <salman@cs.columbia.edu>, Henning Schulzrinne <hgs@cs.columbia.edu>, Thomas Schmidt <Schmidt@informatik.haw-hamburg.de>
>>
>>
>> Hi,
>>
>> The IETF datatracker draft submission service has received your draft
>> draft-ietf-p2psip-sip-13, and requires a
>> confirmation step in order to be able to complete the posting of
>> the draft.
>>
>> Please follow this link to the page where you can confirm the posting:
>>
>> http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d172f5975b09068/
>>
>>
>> Best regards,
>>
>> 	The IETF Secretariat
>> 	through the draft submission service
>>
>>
>>
>>
>

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °


From nobody Mon Jul 21 13:10:54 2014
Return-Path: <br@brianrosen.net>
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 90AC21A0406 for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 13:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level: 
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] 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 YPGUDMSVAjNp for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 13:10:44 -0700 (PDT)
Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7587B1A03FF for <p2psip@ietf.org>; Mon, 21 Jul 2014 13:10:44 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id k15so5720004qaq.27 for <p2psip@ietf.org>; Mon, 21 Jul 2014 13:10:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ZA+bz4SzGO6YJQJYdTVofoGrkKZT8mPzDuk/iBsDCbY=; b=fVao05FEddDLwgKv2xECnKod89GAVPzO0ChLUgxef+8LK7p5vYKCrsAAVjFEZ4/vJM Vg7OyMpl2ghR7h/ENV6nJ7BdRVOKxCIy3M6s/cel0V5qIhMOBLITGdGXsi1sIP/5f4Va QbO0Gqr0NWegzO2+Hw4oxUi0dIi0zHl2i1WNtGrmUZr2yvQ7QfjhD37ZJqIETwBLOrav OPfbg0/2FVTGDycnJSra3gPH4N1zMcjU0K9U9sdKf3rbVrIxyKFmlhphp8S97IgCBt3O xajRlzdGugbvIhmPglKmih1FHIRkgWTexFS+jUHuAOTQIBHiTeKQFo56C1I8rOQCbmWO URHQ==
X-Gm-Message-State: ALoCoQn3ulS024Jg4FbsGT5NL5YpQAELGMXCMnBD1Du0sk4vf/fu5Uf4UMRslvbc1q3DTb+y4qHn
X-Received: by 10.140.104.49 with SMTP id z46mr42338487qge.74.1405973443636; Mon, 21 Jul 2014 13:10:43 -0700 (PDT)
Received: from [156.154.7.47] ([209.173.57.233]) by mx.google.com with ESMTPSA id h5sm17169101qgf.19.2014.07.21.13.10.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jul 2014 13:10:43 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <53CD6AC6.4040908@informatik.haw-hamburg.de>
Date: Mon, 21 Jul 2014 16:10:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net> <53CD6AC6.4040908@informatik.haw-hamburg.de>
To: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/gfNWBqRnIaMjBgjPDcL9OLmCC-4
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
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: Mon, 21 Jul 2014 20:10:52 -0000

I understood differently.  I understood the document to be behind the =
reality of RELOAD.

If I=92m incorrect, we certainly can shepherd it through the process.

Brian

On Jul 21, 2014, at 3:32 PM, Thomas C. Schmidt =
<schmidt@informatik.haw-hamburg.de> wrote:

> Hi Brian,
>=20
> from my understanding, the document is finished in the WG. I guess it =
mainly needs a shepherd for going on, or what do you refer to?
>=20
> Thanks,
>=20
> Thomas
>=20
>=20
>=20
> On 21.07.2014 15:26, Brian Rosen wrote:
>> If there is anyone with energy to finish this document, I think it =
would be good to do so.  But unless someone steps up to the task of =
getting it done and through the process, I think we ought to abandon it.
>>=20
>> Brian
>>=20
>> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt =
<schmidt@informatik.haw-hamburg.de> wrote:
>>=20
>>> Hi Chairs,
>>>=20
>>> I wonder about moving this document?
>>>=20
>>> It has been ready in so loop since a long time ... same goes for =
draft-ietf-p2psip-share-03.
>>>=20
>>> How are plans?
>>>=20
>>> Thanks,
>>>=20
>>> Thomas
>>>=20
>>> -------- Original Message --------
>>> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
>>> Date: Mon, 21 Jul 2014 11:40:00 -0700
>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp =
<bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset =
<salman@cs.columbia.edu>, Henning Schulzrinne <hgs@cs.columbia.edu>, =
Thomas Schmidt <Schmidt@informatik.haw-hamburg.de>
>>>=20
>>>=20
>>> Hi,
>>>=20
>>> The IETF datatracker draft submission service has received your =
draft
>>> draft-ietf-p2psip-sip-13, and requires a
>>> confirmation step in order to be able to complete the posting of
>>> the draft.
>>>=20
>>> Please follow this link to the page where you can confirm the =
posting:
>>>=20
>>> =
http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d=
172f5975b09068/
>>>=20
>>>=20
>>> Best regards,
>>>=20
>>> 	The IETF Secretariat
>>> 	through the draft submission service
>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>=20
> --=20
>=20
> Prof. Dr. Thomas C. Schmidt
> =B0 Hamburg University of Applied Sciences                   Berliner =
Tor 7 =B0
> =B0 Dept. Informatik, Internet Technologies Group    20099 Hamburg, =
Germany =B0
> =B0 http://www.haw-hamburg.de/inet                   Fon: =
+49-40-42875-8452 =B0
> =B0 http://www.informatik.haw-hamburg.de/~schmidt    Fax: =
+49-40-42875-8409 =B0


From nobody Mon Jul 21 13:18:22 2014
Return-Path: <cjbc@it.uc3m.es>
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 298CA1A024C for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 13:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.902
X-Spam-Level: 
X-Spam-Status: No, score=-3.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 eb90rZCKS1YK for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 13:18:16 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7717C1A023E for <p2psip@ietf.org>; Mon, 21 Jul 2014 13:18:14 -0700 (PDT)
Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id CAFBFD230A6; Mon, 21 Jul 2014 22:18:12 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [31.133.179.5] (dhcp-b305.meeting.ietf.org [31.133.179.5]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp01.uc3m.es) by smtp01.uc3m.es (Postfix) with ESMTPSA id 225F9D23037; Mon, 21 Jul 2014 22:18:12 +0200 (CEST)
Message-ID: <1405973890.21180.29.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: Brian Rosen <br@brianrosen.net>
Date: Mon, 21 Jul 2014 22:18:10 +0200
In-Reply-To: <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net> <53CD6AC6.4040908@informatik.haw-hamburg.de> <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.5-2+b3 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.5.0.1018-20832.002
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/i6CD-V_5F581DoRDIvRZkWX2GoY
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cjbc@it.uc3m.es
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: Mon, 21 Jul 2014 20:18:19 -0000

On Mon, 2014-07-21 at 16:10 -0400, Brian Rosen wrote:
> I understood differently.  I understood the document to be behind the reality of RELOAD.
> 
> If Iâ€™m incorrect, we certainly can shepherd it through the process.

And if that is the case, we actually need several reviews of the
document from the WG to make progress.

Carlos

> 
> Brian
> 
> On Jul 21, 2014, at 3:32 PM, Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de> wrote:
> 
> > Hi Brian,
> > 
> > from my understanding, the document is finished in the WG. I guess it mainly needs a shepherd for going on, or what do you refer to?
> > 
> > Thanks,
> > 
> > Thomas
> > 
> > 
> > 
> > On 21.07.2014 15:26, Brian Rosen wrote:
> >> If there is anyone with energy to finish this document, I think it would be good to do so.  But unless someone steps up to the task of getting it done and through the process, I think we ought to abandon it.
> >> 
> >> Brian
> >> 
> >> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de> wrote:
> >> 
> >>> Hi Chairs,
> >>> 
> >>> I wonder about moving this document?
> >>> 
> >>> It has been ready in so loop since a long time ... same goes for draft-ietf-p2psip-share-03.
> >>> 
> >>> How are plans?
> >>> 
> >>> Thanks,
> >>> 
> >>> Thomas
> >>> 
> >>> -------- Original Message --------
> >>> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
> >>> Date: Mon, 21 Jul 2014 11:40:00 -0700
> >>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> >>> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp <bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset <salman@cs.columbia.edu>, Henning Schulzrinne <hgs@cs.columbia.edu>, Thomas Schmidt <Schmidt@informatik.haw-hamburg.de>
> >>> 
> >>> 
> >>> Hi,
> >>> 
> >>> The IETF datatracker draft submission service has received your draft
> >>> draft-ietf-p2psip-sip-13, and requires a
> >>> confirmation step in order to be able to complete the posting of
> >>> the draft.
> >>> 
> >>> Please follow this link to the page where you can confirm the posting:
> >>> 
> >>> http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d172f5975b09068/
> >>> 
> >>> 
> >>> Best regards,
> >>> 
> >>> 	The IETF Secretariat
> >>> 	through the draft submission service
> >>> 
> >>> 
> >>> 
> >>> 
> >> 
> > 
> > -- 
> > 
> > Prof. Dr. Thomas C. Schmidt
> > Â° Hamburg University of Applied Sciences                   Berliner Tor 7 Â°
> > Â° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany Â°
> > Â° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 Â°
> > Â° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 Â°
> 



From nobody Mon Jul 21 13:21:05 2014
Return-Path: <schmidt@informatik.haw-hamburg.de>
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 BCF141A023E for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 13:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001] 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 IJRSXCbPGXJq for <p2psip@ietfa.amsl.com>; Mon, 21 Jul 2014 13:20:59 -0700 (PDT)
Received: from mail1.rz.htw-berlin.de (mail1.rz.htw-berlin.de [141.45.10.101]) (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 037E91A01DC for <p2psip@ietf.org>; Mon, 21 Jul 2014 13:20:59 -0700 (PDT)
Envelope-to: p2psip@ietf.org
Received: from dhcp-a74b.meeting.ietf.org ([31.133.167.75]) by mail1.rz.htw-berlin.de with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1X9K4t-000GXT-Sl; Mon, 21 Jul 2014 22:20:56 +0200
Message-ID: <53CD7626.2090908@informatik.haw-hamburg.de>
Date: Mon, 21 Jul 2014 16:20:54 -0400
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net> <53CD6AC6.4040908@informatik.haw-hamburg.de> <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net>
In-Reply-To: <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: p2psip@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/p8b9xm3uSK4zbEe-4OmaT0WljU4
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
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: Mon, 21 Jul 2014 20:21:02 -0000

Hi Brian,

I'm not aware that the document is behind RELOAD - but we will check.

I'll be back on this shortly.

Thomas

On 21.07.2014 16:10, Brian Rosen wrote:
> I understood differently.  I understood the document to be behind the reality of RELOAD.
>
> If I’m incorrect, we certainly can shepherd it through the process.
>
> Brian
>
> On Jul 21, 2014, at 3:32 PM, Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de> wrote:
>
>> Hi Brian,
>>
>> from my understanding, the document is finished in the WG. I guess it mainly needs a shepherd for going on, or what do you refer to?
>>
>> Thanks,
>>
>> Thomas
>>
>>
>>
>> On 21.07.2014 15:26, Brian Rosen wrote:
>>> If there is anyone with energy to finish this document, I think it would be good to do so.  But unless someone steps up to the task of getting it done and through the process, I think we ought to abandon it.
>>>
>>> Brian
>>>
>>> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de> wrote:
>>>
>>>> Hi Chairs,
>>>>
>>>> I wonder about moving this document?
>>>>
>>>> It has been ready in so loop since a long time ... same goes for draft-ietf-p2psip-share-03.
>>>>
>>>> How are plans?
>>>>
>>>> Thanks,
>>>>
>>>> Thomas
>>>>
>>>> -------- Original Message --------
>>>> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
>>>> Date: Mon, 21 Jul 2014 11:40:00 -0700
>>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>>> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp <bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset <salman@cs.columbia.edu>, Henning Schulzrinne <hgs@cs.columbia.edu>, Thomas Schmidt <Schmidt@informatik.haw-hamburg.de>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> The IETF datatracker draft submission service has received your draft
>>>> draft-ietf-p2psip-sip-13, and requires a
>>>> confirmation step in order to be able to complete the posting of
>>>> the draft.
>>>>
>>>> Please follow this link to the page where you can confirm the posting:
>>>>
>>>> http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d172f5975b09068/
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> 	The IETF Secretariat
>>>> 	through the draft submission service
>>>>
>>>>
>>>>
>>>>
>>>
>>
>> --
>>
>> Prof. Dr. Thomas C. Schmidt
>> ° Hamburg University of Applied Sciences                   Berliner Tor 7 °
>> ° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
>> ° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
>> ° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °
>

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °


From nobody Thu Jul 24 12:21:58 2014
Return-Path: <schmidt@informatik.haw-hamburg.de>
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 6EFCE1B2830 for <p2psip@ietfa.amsl.com>; Thu, 24 Jul 2014 12:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001] 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 JmeaBw5ahJJh for <p2psip@ietfa.amsl.com>; Thu, 24 Jul 2014 12:21:53 -0700 (PDT)
Received: from mail1.rz.htw-berlin.de (mail1.rz.htw-berlin.de [141.45.10.101]) (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 9469A1A03A5 for <p2psip@ietf.org>; Thu, 24 Jul 2014 12:21:53 -0700 (PDT)
Envelope-to: p2psip@ietf.org
Received: from dhcp-a6ca.meeting.ietf.org ([31.133.166.202]) by mail1.rz.htw-berlin.de with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1XAOaL-000OgI-Ps; Thu, 24 Jul 2014 21:21:50 +0200
Message-ID: <53D15CC9.7070605@informatik.haw-hamburg.de>
Date: Thu, 24 Jul 2014 15:21:45 -0400
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net> <53CD6AC6.4040908@informatik.haw-hamburg.de> <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net> <53CD7626.2090908@informatik.haw-hamburg.de>
In-Reply-To: <53CD7626.2090908@informatik.haw-hamburg.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: p2psip@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/6i9M4N4MIlVIGbGFsj-U9FPz7Kg
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
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: Thu, 24 Jul 2014 19:21:55 -0000

Hi Brian, Carlos,

so we checked back also with Marc about any late changes in RELOAD. 
There is nothing that puts SIP or ShaRE behind RELOAD.

Both drafts are ready and wait for shepherding: they had WG reviews and 
implementations ... I believe they can just go.

Thomas

On 21.07.2014 16:20, Thomas C. Schmidt wrote:
> Hi Brian,
>
> I'm not aware that the document is behind RELOAD - but we will check.
>
> I'll be back on this shortly.
>
> Thomas
>
> On 21.07.2014 16:10, Brian Rosen wrote:
>> I understood differently.  I understood the document to be behind the
>> reality of RELOAD.
>>
>> If I’m incorrect, we certainly can shepherd it through the process.
>>
>> Brian
>>
>> On Jul 21, 2014, at 3:32 PM, Thomas C. Schmidt
>> <schmidt@informatik.haw-hamburg.de> wrote:
>>
>>> Hi Brian,
>>>
>>> from my understanding, the document is finished in the WG. I guess it
>>> mainly needs a shepherd for going on, or what do you refer to?
>>>
>>> Thanks,
>>>
>>> Thomas
>>>
>>>
>>>
>>> On 21.07.2014 15:26, Brian Rosen wrote:
>>>> If there is anyone with energy to finish this document, I think it
>>>> would be good to do so.  But unless someone steps up to the task of
>>>> getting it done and through the process, I think we ought to abandon
>>>> it.
>>>>
>>>> Brian
>>>>
>>>> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt
>>>> <schmidt@informatik.haw-hamburg.de> wrote:
>>>>
>>>>> Hi Chairs,
>>>>>
>>>>> I wonder about moving this document?
>>>>>
>>>>> It has been ready in so loop since a long time ... same goes for
>>>>> draft-ietf-p2psip-share-03.
>>>>>
>>>>> How are plans?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Thomas
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
>>>>> Date: Mon, 21 Jul 2014 11:40:00 -0700
>>>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>>>> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp
>>>>> <bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset
>>>>> <salman@cs.columbia.edu>, Henning Schulzrinne
>>>>> <hgs@cs.columbia.edu>, Thomas Schmidt
>>>>> <Schmidt@informatik.haw-hamburg.de>
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> The IETF datatracker draft submission service has received your draft
>>>>> draft-ietf-p2psip-sip-13, and requires a
>>>>> confirmation step in order to be able to complete the posting of
>>>>> the draft.
>>>>>
>>>>> Please follow this link to the page where you can confirm the posting:
>>>>>
>>>>> http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d172f5975b09068/
>>>>>
>>>>>
>>>>>
>>>>> Best regards,
>>>>>
>>>>>     The IETF Secretariat
>>>>>     through the draft submission service
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> --
>>>
>>> Prof. Dr. Thomas C. Schmidt
>>> ° Hamburg University of Applied Sciences                   Berliner
>>> Tor 7 °
>>> ° Dept. Informatik, Internet Technologies Group    20099 Hamburg,
>>> Germany °
>>> ° http://www.haw-hamburg.de/inet                   Fon:
>>> +49-40-42875-8452 °
>>> ° http://www.informatik.haw-hamburg.de/~schmidt    Fax:
>>> +49-40-42875-8409 °
>>
>

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °


From nobody Thu Jul 24 13:39:24 2014
Return-Path: <br@brianrosen.net>
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 C09BC1B28D5 for <p2psip@ietfa.amsl.com>; Thu, 24 Jul 2014 13:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.821
X-Spam-Level: 
X-Spam-Status: No, score=-1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] 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 Bb591jifAmpw for <p2psip@ietfa.amsl.com>; Thu, 24 Jul 2014 13:39:20 -0700 (PDT)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 698231B28D6 for <p2psip@ietf.org>; Thu, 24 Jul 2014 13:39:18 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id n3so4683980wiv.13 for <p2psip@ietf.org>; Thu, 24 Jul 2014 13:39:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=c0cwSEMOJ7Ykrwl/9G7AVZu0QsTBsPxZTry/65MecS4=; b=MAMk6q2bt1vBT8V1PZ0wZO/4n4vLZ2ep/02jUc96Y6ElHfbA7u7wsr9ZZVGEsMOZpz 7SYmN7p3+wrjWKUYtwoIsLqeqKZkh96q93EI9C7wCu/F2P+HQJTUBi1uTZ1uD0jBh8Mf pfsoFTDxJ4hn/yTubCvHIhvb4/8eHuJYJFUlzdZ6yUkK1+H/PfaRHqQhf4hwpntJ2bWf gKlbWFIBTnQEfMULg/UmdPoOGCZL/Xt0bQ1ZNrdvgrYDlB1X/nzYLUAxMQUHRxFh6Alt 18JNJSG/Mn+qNvtdX6FH5dCAH3olUTQO9C5hw8qW7mgUGqtxD7lgRXKOYZFCK8kTL9c3 CWCQ==
X-Gm-Message-State: ALoCoQnO0hPs23mdaNSlngs+2TycgsBpVJBnudi8Pvi5H6grgGbk2be1gvX7CzXXVQewVHwPBRQT
X-Received: by 10.180.106.66 with SMTP id gs2mr16714706wib.5.1406234356880; Thu, 24 Jul 2014 13:39:16 -0700 (PDT)
Received: from wireless-a-v6.meeting.ietf.org ([2001:67c:370:176:858c:7:8133:991d]) by mx.google.com with ESMTPSA id cz4sm27137017wib.23.2014.07.24.13.39.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jul 2014 13:39:16 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <53D15CC9.7070605@informatik.haw-hamburg.de>
Date: Thu, 24 Jul 2014 16:39:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F28B55E-8D50-49B3-945E-6A274CC83127@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net> <53CD6AC6.4040908@informatik.haw-hamburg.de> <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net> <53CD7626.2090908@informatik.haw-hamburg.de> <53D15CC9.7070605@informatik.haw-hamburg.de>
To: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/UocmvvbW4tOtWWBkYl-x3S0iOr4
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
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: Thu, 24 Jul 2014 20:39:22 -0000

That=92s great.  We=92ll move the drafts forward.

Brian

On Jul 24, 2014, at 3:21 PM, Thomas C. Schmidt =
<schmidt@informatik.haw-hamburg.de> wrote:

> Hi Brian, Carlos,
>=20
> so we checked back also with Marc about any late changes in RELOAD. =
There is nothing that puts SIP or ShaRE behind RELOAD.
>=20
> Both drafts are ready and wait for shepherding: they had WG reviews =
and implementations ... I believe they can just go.
>=20
> Thomas
>=20
> On 21.07.2014 16:20, Thomas C. Schmidt wrote:
>> Hi Brian,
>>=20
>> I'm not aware that the document is behind RELOAD - but we will check.
>>=20
>> I'll be back on this shortly.
>>=20
>> Thomas
>>=20
>> On 21.07.2014 16:10, Brian Rosen wrote:
>>> I understood differently.  I understood the document to be behind =
the
>>> reality of RELOAD.
>>>=20
>>> If I=92m incorrect, we certainly can shepherd it through the =
process.
>>>=20
>>> Brian
>>>=20
>>> On Jul 21, 2014, at 3:32 PM, Thomas C. Schmidt
>>> <schmidt@informatik.haw-hamburg.de> wrote:
>>>=20
>>>> Hi Brian,
>>>>=20
>>>> from my understanding, the document is finished in the WG. I guess =
it
>>>> mainly needs a shepherd for going on, or what do you refer to?
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Thomas
>>>>=20
>>>>=20
>>>>=20
>>>> On 21.07.2014 15:26, Brian Rosen wrote:
>>>>> If there is anyone with energy to finish this document, I think it
>>>>> would be good to do so.  But unless someone steps up to the task =
of
>>>>> getting it done and through the process, I think we ought to =
abandon
>>>>> it.
>>>>>=20
>>>>> Brian
>>>>>=20
>>>>> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt
>>>>> <schmidt@informatik.haw-hamburg.de> wrote:
>>>>>=20
>>>>>> Hi Chairs,
>>>>>>=20
>>>>>> I wonder about moving this document?
>>>>>>=20
>>>>>> It has been ready in so loop since a long time ... same goes for
>>>>>> draft-ietf-p2psip-share-03.
>>>>>>=20
>>>>>> How are plans?
>>>>>>=20
>>>>>> Thanks,
>>>>>>=20
>>>>>> Thomas
>>>>>>=20
>>>>>> -------- Original Message --------
>>>>>> Subject: Confirm submission of I-D draft-ietf-p2psip-sip
>>>>>> Date: Mon, 21 Jul 2014 11:40:00 -0700
>>>>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>>>>> To: Cullen Jennings <fluffy@cisco.com>, Bruce Lowekamp
>>>>>> <bbl@lowekamp.net>, Eric Rescorla <ekr@rtfm.com>, Salman Baset
>>>>>> <salman@cs.columbia.edu>, Henning Schulzrinne
>>>>>> <hgs@cs.columbia.edu>, Thomas Schmidt
>>>>>> <Schmidt@informatik.haw-hamburg.de>
>>>>>>=20
>>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> The IETF datatracker draft submission service has received your =
draft
>>>>>> draft-ietf-p2psip-sip-13, and requires a
>>>>>> confirmation step in order to be able to complete the posting of
>>>>>> the draft.
>>>>>>=20
>>>>>> Please follow this link to the page where you can confirm the =
posting:
>>>>>>=20
>>>>>> =
http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d=
172f5975b09068/
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Best regards,
>>>>>>=20
>>>>>>    The IETF Secretariat
>>>>>>    through the draft submission service
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>> --
>>>>=20
>>>> Prof. Dr. Thomas C. Schmidt
>>>> =B0 Hamburg University of Applied Sciences                   =
Berliner
>>>> Tor 7 =B0
>>>> =B0 Dept. Informatik, Internet Technologies Group    20099 Hamburg,
>>>> Germany =B0
>>>> =B0 http://www.haw-hamburg.de/inet                   Fon:
>>>> +49-40-42875-8452 =B0
>>>> =B0 http://www.informatik.haw-hamburg.de/~schmidt    Fax:
>>>> +49-40-42875-8409 =B0
>>>=20
>>=20
>=20
> --=20
>=20
> Prof. Dr. Thomas C. Schmidt
> =B0 Hamburg University of Applied Sciences                   Berliner =
Tor 7 =B0
> =B0 Dept. Informatik, Internet Technologies Group    20099 Hamburg, =
Germany =B0
> =B0 http://www.haw-hamburg.de/inet                   Fon: =
+49-40-42875-8452 =B0
> =B0 http://www.informatik.haw-hamburg.de/~schmidt    Fax: =
+49-40-42875-8409 =B0


From nobody Thu Jul 24 13:41:10 2014
Return-Path: <petithug@acm.org>
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 A33071B28DD for <p2psip@ietfa.amsl.com>; Thu, 24 Jul 2014 13:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level: 
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] 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 yuGTTrNjWg6e for <p2psip@ietfa.amsl.com>; Thu, 24 Jul 2014 13:41:07 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8221B28D6 for <p2psip@ietf.org>; Thu, 24 Jul 2014 13:41:07 -0700 (PDT)
Received: from [IPv6:2001:5c0:1000:b::1bb5] (petithug.broker.freenet6.net [IPv6:2001:5c0:1000:b::1bb5]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 6928021676; Thu, 24 Jul 2014 22:41:05 +0200 (CEST)
Message-ID: <53D16F5F.1010002@acm.org>
Date: Thu, 24 Jul 2014 14:41:03 -0600
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0
MIME-Version: 1.0
To: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>,  Brian Rosen <br@brianrosen.net>
References: <20140721184000.22310.54252.idtracker@ietfa.amsl.com> <53CD6050.2030206@informatik.haw-hamburg.de> <B5DCB1B5-ADEE-4520-8A54-2E9EEB1682FC@brianrosen.net> <53CD6AC6.4040908@informatik.haw-hamburg.de> <D24CBC47-3B8D-4373-B0A9-ACA7DBEBE4D7@brianrosen.net> <53CD7626.2090908@informatik.haw-hamburg.de> <53D15CC9.7070605@informatik.haw-hamburg.de>
In-Reply-To: <53D15CC9.7070605@informatik.haw-hamburg.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/VlFyKLH-Efj6UT4LNCuWnUn-RRA
Cc: p2psip@ietf.org
Subject: Re: [P2PSIP] submission of I-D draft-ietf-p2psip-sip
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: Thu, 24 Jul 2014 20:41:08 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Yes, I read again the lastest versions of p2psip-sip and p2psip-share, and did
not find anything in them that is behind RFC 6940.

On 07/24/2014 01:21 PM, Thomas C. Schmidt wrote:
> Hi Brian, Carlos,
> 
> so we checked back also with Marc about any late changes in RELOAD. There
> is nothing that puts SIP or ShaRE behind RELOAD.
> 
> Both drafts are ready and wait for shepherding: they had WG reviews and 
> implementations ... I believe they can just go.
> 
> Thomas
> 
> On 21.07.2014 16:20, Thomas C. Schmidt wrote:
>> Hi Brian,
>> 
>> I'm not aware that the document is behind RELOAD - but we will check.
>> 
>> I'll be back on this shortly.
>> 
>> Thomas
>> 
>> On 21.07.2014 16:10, Brian Rosen wrote:
>>> I understood differently.  I understood the document to be behind the 
>>> reality of RELOAD.
>>> 
>>> If Iâ€™m incorrect, we certainly can shepherd it through the process.
>>> 
>>> Brian
>>> 
>>> On Jul 21, 2014, at 3:32 PM, Thomas C. Schmidt 
>>> <schmidt@informatik.haw-hamburg.de> wrote:
>>> 
>>>> Hi Brian,
>>>> 
>>>> from my understanding, the document is finished in the WG. I guess
>>>> it mainly needs a shepherd for going on, or what do you refer to?
>>>> 
>>>> Thanks,
>>>> 
>>>> Thomas
>>>> 
>>>> 
>>>> 
>>>> On 21.07.2014 15:26, Brian Rosen wrote:
>>>>> If there is anyone with energy to finish this document, I think it 
>>>>> would be good to do so.  But unless someone steps up to the task
>>>>> of getting it done and through the process, I think we ought to
>>>>> abandon it.
>>>>> 
>>>>> Brian
>>>>> 
>>>>> On Jul 21, 2014, at 2:47 PM, Thomas C. Schmidt 
>>>>> <schmidt@informatik.haw-hamburg.de> wrote:
>>>>> 
>>>>>> Hi Chairs,
>>>>>> 
>>>>>> I wonder about moving this document?
>>>>>> 
>>>>>> It has been ready in so loop since a long time ... same goes for 
>>>>>> draft-ietf-p2psip-share-03.
>>>>>> 
>>>>>> How are plans?
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Thomas
>>>>>> 
>>>>>> -------- Original Message -------- Subject: Confirm submission of
>>>>>> I-D draft-ietf-p2psip-sip Date: Mon, 21 Jul 2014 11:40:00 -0700 
>>>>>> From: IETF I-D Submission Tool <idsubmission@ietf.org> To: Cullen
>>>>>> Jennings <fluffy@cisco.com>, Bruce Lowekamp <bbl@lowekamp.net>,
>>>>>> Eric Rescorla <ekr@rtfm.com>, Salman Baset 
>>>>>> <salman@cs.columbia.edu>, Henning Schulzrinne 
>>>>>> <hgs@cs.columbia.edu>, Thomas Schmidt 
>>>>>> <Schmidt@informatik.haw-hamburg.de>
>>>>>> 
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> The IETF datatracker draft submission service has received your
>>>>>> draft draft-ietf-p2psip-sip-13, and requires a confirmation step
>>>>>> in order to be able to complete the posting of the draft.
>>>>>> 
>>>>>> Please follow this link to the page where you can confirm the
>>>>>> posting:
>>>>>> 
>>>>>> http://datatracker.ietf.org/submit/status/61861/confirm/8fe6d2cf87c2c2b66d172f5975b09068/
>>>>>>
>>>>>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJT0W9eAAoJECnERZXWan7Ei4EP/3feyjn7uRP1impVWfVrl8ac
CTBsxEyp0ON0pBWonXSb2E9LsVeWWiUZZzLpk75mQeUgGMGu+EUZdH1DL0ip8pIW
DgONGHwO5C/6gLaxkBSpX6/I/8L+jQY1go+oR4wLAiBI8L1E2XItnoEznNBDwUx0
W/m3PHPP5vqdrQTemLF8h7tmzwk1l269PROb4fS84TAZcjDx0edLWzYii3bfLMfi
hngtRKhpbxpmCeS68C7GKqoue6dR7tEBbOPOazf0dRUpijMSBOKh5GZKBUQYrhqP
sdClI6gBadb4uyxiJWkQK5qcX3LDK63zagBp+mw6oiNymwcagVVlgIxdQZ0lz8TP
MgELcx3jsd11fO5BMQqqASdMlWAZC87r99T+sZAfFaRAAe7QWeAwMWxK1qUwmkKX
HKlHylK9eIVnX1T5d0utS7/WKoQQmfZq4RjTCImbqJpyTp3Q2+8N49ExzaLgP6ln
1lvVcCjt//dan7H/sc40tjWs4QZvfDf/0BpThsTAGTrQzk/bEEwWToKuBKoX7Q0d
Du6LeZRFp/3W/JvUVB+YkRgmIHv2fAF71CDbyvllVcclRbm9HtmM2+TQYwRmPgtC
EPx1hmQ2tsscFTMtMVmtha164o4IJs/I8cywsi/+uh8OrHBFz1OlhR9ihxONuZ7V
/HrKzN5KM+Fhr+xiusav
=Pusk
-----END PGP SIGNATURE-----


From nobody Fri Jul 25 08:31:18 2014
Return-Path: <iesg-secretary@ietf.org>
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 AF6A51B2986; Fri, 25 Jul 2014 08:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 EjmmciaJ29LZ; Fri, 25 Jul 2014 08:31:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA5E81B299A; Fri, 25 Jul 2014 08:31:10 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140725153110.17642.93929.idtracker@ietfa.amsl.com>
Date: Fri, 25 Jul 2014 08:31:10 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/1reO6FCeHMkVUdBKs9fj9jvgL4g
Cc: p2psip chair <p2psip-chairs@tools.ietf.org>, p2psip mailing list <p2psip@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [P2PSIP] Protocol Action: 'Self-tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)' to Proposed Standard (draft-ietf-p2psip-self-tuning-15.txt)
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 25 Jul 2014 15:31:14 -0000

The IESG has approved the following document:
- 'Self-tuning Distributed Hash Table (DHT) for REsource LOcation And
   Discovery (RELOAD)'
  (draft-ietf-p2psip-self-tuning-15.txt) as Proposed Standard

This document is the product of the Peer-to-Peer Session Initiation
Protocol Working Group.

The IESG contact persons are Alissa Cooper and Richard Barnes.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-p2psip-self-tuning/




Technical Summary:

Peers in a RELOAD overlay network collectively run an overlay algorithm to
organize the overlay, and to store and retrieve data. This document describes
an extension to the default topology plugin of RELOAD to support self-tuning,
meaning to make it capable of adapting to changing operating conditions such as
churn and network size.

Working Group Summary:

The normal WG process was followed and the document has been discussed for
several years. The document as it is now, reflects WG consensus, with nothing
special worth noting.

Document Quality:

The document was thoroughly reviewed by Marc Petit-Huguenin and Carlos J.
Bernardos.

Personnel:

Carlos J. Bernardos is the document shepherd. Alissa Cooper is the responsible area director.


From nobody Fri Jul 25 09:50:14 2014
Return-Path: <cjbc@it.uc3m.es>
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 38C851B290F for <p2psip@ietfa.amsl.com>; Fri, 25 Jul 2014 09:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.902
X-Spam-Level: 
X-Spam-Status: No, score=-3.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 Ue7-0imx77yg for <p2psip@ietfa.amsl.com>; Fri, 25 Jul 2014 09:50:08 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B9E61B27D8 for <p2psip@ietf.org>; Fri, 25 Jul 2014 09:50:08 -0700 (PDT)
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id CC63E11156AB; Fri, 25 Jul 2014 18:50:04 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [31.133.168.144] (dhcp-a890.meeting.ietf.org [31.133.168.144]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 3624B1185245; Fri, 25 Jul 2014 18:50:04 +0200 (CEST)
Message-ID: <1406307002.10492.15.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: p2psip@ietf.org
Date: Fri, 25 Jul 2014 18:50:02 +0200
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.5-2+b3 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.5.0.1018-20840.000
X-TM-AS-Result: No--3.963-7.0-31-1
X-imss-scan-details: No--3.963-7.0-31-1
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/Dn7wN9n3vw7begSDqPr4GZK4AI8
Cc: p2psip-chairs@tools.ietf.org
Subject: [P2PSIP] WGLC for draft-ietf-p2psip-sip-13
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cjbc@it.uc3m.es
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: Fri, 25 Jul 2014 16:50:11 -0000

Hi,

Hereby we are issuing a WGLC for draft-ietf-p2psip-sip-13. We did one
back in May 2013, so we want to ensure that everything is fine from the
point of view of the WG.

The WGLC will be open till the 8th of September, so we have time enough
even there is August in the middle. We kindly ask the WG to review the
document and provide comments.

If you have no comments and think the document is ready to be submitted 
to IESG, please do send a note stating that to the WG ML.

Additional information about the document is below:

        Title           : A SIP Usage for RELOAD
        Authors         : Cullen Jennings
                          Bruce B. Lowekamp
                          Eric Rescorla
                          Salman A. Baset
                          Henning Schulzrinne
                          Thomas C. Schmidt
        Filename        : draft-ietf-p2psip-sip-13.txt
        Pages           : 20
        Date            : 2014-07-21

Abstract:
   This document defines a SIP Usage for REsource LOcation And Discovery
   (RELOAD).  The SIP Usage provides the functionality of a SIP proxy or
   registrar in a fully-distributed system and includes a lookup service
   for Address of Records (AORs) stored in the overlay.  It also defines
   Globally Routable User Agent Uris (GRUUs) that allow the
   registrations to map an AOR to a specific node reachable through the
   overlay.  After such initial contact of a peer, the AppAttach method
   is used to establish a direct connection between nodes through which
   SIP messages are exchanged.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-p2psip-sip/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-p2psip-sip-13

Thanks

-- Brian and Carlos


From nobody Tue Jul 29 03:53:37 2014
Return-Path: <internet-drafts@ietf.org>
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 57A851B27A6; Tue, 29 Jul 2014 03:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 vwpVdsDy1qb7; Tue, 29 Jul 2014 03:53:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 34EDB1B2795; Tue, 29 Jul 2014 03:53:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140729105332.22499.83870.idtracker@ietfa.amsl.com>
Date: Tue, 29 Jul 2014 03:53:32 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/p2psip/BvGRytyrwq43nC6GNk0BaC4huKc
Cc: p2psip@ietf.org
Subject: [P2PSIP] I-D Action: draft-ietf-p2psip-service-discovery-14.txt
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Jul 2014 10:53:33 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF.

        Title           : Service Discovery Usage for REsource LOcation And Discovery (RELOAD)
        Authors         : Jouni Maenpaa
                          Gonzalo Camarillo
	Filename        : draft-ietf-p2psip-service-discovery-14.txt
	Pages           : 20
	Date            : 2014-07-29

Abstract:
   REsource LOcation and Discovery (RELOAD) does not define a generic
   service discovery mechanism as a part of the base protocol.  This
   document defines how the Recursive Distributed Rendezvous (ReDiR)
   service discovery mechanism used in OpenDHT can be applied to RELOAD
   overlays to provide a generic service discovery mechanism.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-p2psip-service-discovery/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-p2psip-service-discovery-14

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-p2psip-service-discovery-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

