IETF Logo Mail Archive

RE: [P2PSIP] HIP: optional, mandatory?

"Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil> Wed, 23 January 2008 14:15 UTC

Return-path: <p2psip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHgNj-00005c-NO; Wed, 23 Jan 2008 09:15:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHgNi-00005K-D1 for p2psip@ietf.org; Wed, 23 Jan 2008 09:15:10 -0500
Received: from mxoutps1.us.army.mil ([143.69.250.38]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHgNd-0008R4-Pp for p2psip@ietf.org; Wed, 23 Jan 2008 09:15:10 -0500
DomainKey-Signature: s=ako; d=us.army.mil; c=nofws; q=dns; h=From:X-AKO:X-IronPort-AV:Received:Received:To:Cc: Message-ID:Date:X-Mailer:MIME-Version:Content-Language: Subject:X-Accept-Language:Priority:In-Reply-To:References: Content-Type:Content-Disposition: Content-Transfer-Encoding; b=T28yheQbOiuKqmV6cZRe1z5x41yWBao+84+v3xj5ZivV9zZ57cNNuMq7 G13wvHAzmPk+QuicVs7hSE3phB4ZPQ==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 105926420:10.224.36.65:23 Jan 2008 14:15:01 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,238,1199664000"; d="scan'208";a="105926420"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65]) by mxoutps1.us.army.mil with ESMTP; 23 Jan 2008 14:15:01 +0000
Received: from [10.240.32.176] (Forwarded-For: 134.80.13.193, [10.240.32.176]) by mail5.int.ps1.us.army.mil (mshttpd); Wed, 23 Jan 2008 09:15:01 -0500
To: marcin.matuszewski@nokia.com
Message-ID: <e044864a19844.47970595@us.army.mil>
Date: Wed, 23 Jan 2008 09:15:01 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11 2007)
MIME-Version: 1.0
Content-Language: en
Subject: RE: [P2PSIP] HIP: optional, mandatory?
X-Accept-Language: en
Priority: normal
In-Reply-To: <3F18E76823C95E4795181D74BAC7664F05BE199F@esebe102.NOE.Nokia.com>
References: <476BA8D9.4010203@ericsson.com> <20d2bdfb0712210823m2218c4a6mcace60af3d82db57@mail.gmail.com> <476E2B7C.9070601@ericsson.com> <20d2bdfb0801081416t41b9b84atb3a147659771036@mail.gmail.com> <77F357662F8BFA4CA7074B0410171B6D04049B22@XCH-NW-5V1.nw.nos.boeing.com> <7C5B8529-85C9-4977-8C57-34E9041ED1EC@nomadiclab.com> <77F357662F8BFA4CA7074B0410171B6D04049B33@XCH-NW-5V1.nw.nos.boeing.com> <10DA6CAF-DB5B-4B89-9417-4BEFD816B1E5@cs.columbia.edu> <4571B070-0B2F-4076-AAAB-4398295C9E88@cisco.com> <465FBE4D-F548-4D7C-855C-10498AF22E6C@quinthar.com> <284DBC3B-BF18-400D-8D00-3EB367AEAAA3@cisco.com> <DD40D2FF-809B-4B1F-B43B-0E8F41ED21DB@quinthar.com> <24CCCC428EFEA2469BF046DB3C7A8D223AE531@namail5.corp.adobe.com> <3F18E76823C95E4795181D74BAC7664F05B951F1@esebe102.NOE.Nokia.com> <e3c8ad9a1429b.47946208@us.army.mil> <3F18E76823C95E4795181D74BAC7664F05B95CF4@esebe102.NOE.Nokia.com> <d4accb881f22e.4795b446@us.army.mil> <3F18E76823C95E4795181D74BAC7664F05BE199F@esebe102.NOE.Nokia.com>
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: p2psip@ietf.org
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
Errors-To: p2psip-bounces@ietf.org

Marcin:

Yes, that is what this WG, I believe, wants - helping to finalize the base P2PSIP protocol through implementation experiences as soon as possible.

Best regards,
Radhika

----- Original Message -----
From: marcin.matuszewski@nokia.com
Date: Wednesday, January 23, 2008 7:30
Subject: RE: RE: RE: [P2PSIP] HIP: optional, mandatory?
To: radhika.r.roy@us.army.mil
Cc: p2psip@ietf.org, salman@cs.columbia.edu, hgs@cs.columbia.edu, marcin.matuszewski@nokia.com

> Hi Radhika,
> 
> We share the same goal. 
> 
> Salman, Henning and me are specifying the P2PP protocol
> http://tools.ietf.org/wg/p2psip/draft-baset-p2psip-p2pp-01.txt. The
> version of the document is going to be updated based on our recent
> implementation experience. 
> 
> We would appreciate your suggestions and comments. The cooperation on
> software development is also appreciated. This will allow P2PSIP 
> WG to
> converge much faster.
> 
> Marcin
> 
> 
> >-----Original Message-----
> >From: ext Roy, Radhika R Dr CTR USA USAMC 
> >[mailto:radhika.r.roy@us.army.mil] 
> >Sent: 22 January, 2008 16:16
> >To: Matuszewski Marcin (Nokia-NRC/Helsinki)
> >Cc: p2psip@ietf.org; salman@cs.columbia.edu; Matuszewski 
> >Marcin (Nokia-NRC/Helsinki)
> >Subject: Re: RE: RE: [P2PSIP] HIP: optional, mandatory?
> >
> >Hi, Mercin:
> >
> >What we want is to develop the P2PSIP protocol standard for 
> >this WG. The P2PSIP protocol drafts are there. You can help to 
> >provide insights which proposals are good and if needed what 
> >improvements need to be done to finalize the specs or you can 
> >proposed a new one or a modified draft combining with the 
> >existing ones.
> >
> >In this way, you can play a role to standardize the P2PSIP 
> >protocol for this WG. Then we can proceed to build other P2P 
> >things (e.g. HIP-overlay using the standardized P2PSIP 
> >protocol of this WG).
> >
> >Best regards,
> >Radhika
> >

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

v2.23.0 | Report a Bug | By Email