Re: [Sipping] FW: New Versiondraft-vanelburg-sipping-private-network-indication-01

"Leis, Peter (NSN - DE/Muenich)" <peter.leis@nsn.com> Tue, 26 February 2008 08:48 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: ietfarch-sipping-archive@core3.amsl.com
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52F9F28C2C3; Tue, 26 Feb 2008 00:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.207
X-Spam-Level:
X-Spam-Status: No, score=-1.207 tagged_above=-999 required=5 tests=[AWL=-0.770, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwDJNR3TVqc6; Tue, 26 Feb 2008 00:48:12 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 474E528C0D7; Tue, 26 Feb 2008 00:48:12 -0800 (PST)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A9F23A6C20 for <sipping@core3.amsl.com>; Tue, 26 Feb 2008 00:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1lDAcSmcgrD for <sipping@core3.amsl.com>; Tue, 26 Feb 2008 00:48:09 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id 6DEF33A6C1C for <sipping@ietf.org>; Tue, 26 Feb 2008 00:48:09 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id m1Q8m0p7000501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2008 09:48:00 +0100
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id m1Q8lvmR005859; Tue, 26 Feb 2008 09:48:00 +0100
Received: from DEMUEXC005.nsn-intra.net ([10.150.128.17]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 26 Feb 2008 09:47:58 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 26 Feb 2008 09:47:58 +0100
Message-ID: <81D3255A15981A4B912531E3648B1E169258A5@DEMUEXC005.nsn-intra.net>
In-Reply-To: <2C685FA24AE8004CA8F0DCCC7AF6AD0801C4FB26@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] FW: New Versiondraft-vanelburg-sipping-private-network-indication-01
Thread-Index: Ach1rcdsygjM1DEQRHm0bSg5AXSnLQABfREgAKe5+EA=
References: <2C685FA24AE8004CA8F0DCCC7AF6AD0801C4FB26@esealmw109.eemea.ericsson.se>
From: "Leis, Peter (NSN - DE/Muenich)" <peter.leis@nsn.com>
To: sipping@ietf.org
X-OriginalArrivalTime: 26 Feb 2008 08:47:58.0979 (UTC) FILETIME=[49BD5530:01C87854]
Subject: Re: [Sipping] FW: New Versiondraft-vanelburg-sipping-private-network-indication-01
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

 Hans Erik

some comments

7.2.1
I don't understand why incoming public traffic to a corporate needs to
be marked as Private. I thought the "private" indication is only usefull
in public networks.

7.2.2
- "MUST support" this extension is rather vague. What is the real
requirement here in terms of protocol usage? Are there any procedures
expected to happen in the proxy?

- I propose to add that in case the indication is received from a
entitiy that is not trusted, then the Proxy MUST remove the indication

7.2.3
what is meant with "converting private traffic to public traffic"?  Is
forwarding a request that contains the new indication towards a user
(not beloinging to any corporate) also regarded as "converting private
traffic to public traffic"?


Peter

> -----Original Message-----
> From: sipping-bounces@ietf.org 
> [mailto:sipping-bounces@ietf.org] On Behalf Of ext Hans Erik 
> van Elburg
> Sent: Saturday, February 23, 2008 1:39 AM
> To: sipping@ietf.org
> Subject: [Sipping] FW: New 
> Versiondraft-vanelburg-sipping-private-network-indication-01
> 
> 
> A new version of I-D,
> draft-vanelburg-sipping-private-network-indication-01.txt has been
> successfuly submitted.
> 
> http://tools.ietf.org/html/draft-vanelburg-sipping-private-net
> work-indic
> ation-01
> 
> Revision Information
> - Added a solution based on a new header.  
> - Added Overview, Behaviour and Header Definition sections.  
> - Updated the trust domain definition.  Improved some of the existing
> text
>   based on received comments.
> 
> Filename:	 draft-vanelburg-sipping-private-network-indication
> Revision:	 01
> Title:		 Requirements for explicit private 
> network indication
> Creation_date:	 2008-02-22
> WG ID:		 Independent Submission
> Number_of_pages: 15
> 
> Abstract:
> This document describes why a private network indication is needed.
> A private network indication allows other nodes in a network to treat
> private network traffic to a different set of rules then 
> public network
> traffic.  The indication also distinguishes one private network from
> another private network.
>  
> 
> 
> Best Regards,
> /Hans Erik
> 
> 
> 
> _______________________________________________
> Sipping mailing list  http://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sipping mailing list  http://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP