Re: [Sipping] I-D Action:draft-vanelburg-sipping-private-network-indication-01.txt
"Elwell, John" <john.elwell@siemens.com> Mon, 25 February 2008 16:54 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 EC1A028C563; Mon, 25 Feb 2008 08:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.625
X-Spam-Level:
X-Spam-Status: No, score=-0.625 tagged_above=-999 required=5 tests=[AWL=-0.188, 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 b1qW2tR3uDK2; Mon, 25 Feb 2008 08:54:43 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10B013A6CF6; Mon, 25 Feb 2008 08:54:35 -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 948A43A6C47 for <sipping@core3.amsl.com>; Mon, 25 Feb 2008 08:54:33 -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 uDFnL6Ms0tTC for <sipping@core3.amsl.com>; Mon, 25 Feb 2008 08:54:32 -0800 (PST)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id AC51F28C58C for <sipping@ietf.org>; Mon, 25 Feb 2008 08:52:19 -0800 (PST)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0JWT00G4E071W7@siemenscomms.co.uk> for sipping@ietf.org; Mon, 25 Feb 2008 16:52:13 +0000 (GMT)
Date: Mon, 25 Feb 2008 16:52:14 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <20080223000005.319403A67FB@core3.amsl.com>
To: sipping@ietf.org, Hans Erik van Elburg <hanserik.van.elburg@ericsson.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D06CFD16@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: I-D Action:draft-vanelburg-sipping-private-network-indication-01.txt
thread-index: Ach1ryPDGGh7w049TW6EuOZdQ+Z8RACHv7zw
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <20080223000005.319403A67FB@core3.amsl.com>
Subject: Re: [Sipping] I-D Action:draft-vanelburg-sipping-private-network-indication-01.txt
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, "[Whether the indication is useful on responses requires further discussion.]" and "R2: The indication from R1 can be inserted by a SIP proxy belonging to an administrative entity where for onward routeing, the traffic within that administrative entity needs to be so distinguished." From the latter I would deduce that inclusion of the indicator in responses is not needed - it is only needed in requests if it is needed only for influencing routing. John > -----Original Message----- > From: i-d-announce-bounces@ietf.org > [mailto:i-d-announce-bounces@ietf.org] On Behalf Of > Internet-Drafts@ietf.org > Sent: 23 February 2008 00:00 > To: i-d-announce@ietf.org > Subject: I-D > Action:draft-vanelburg-sipping-private-network-indication-01.txt > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > > Title : Requirements for explicit private > network indication > Author(s) : H. van Elburg, K. Drage > Filename : > draft-vanelburg-sipping-private-network-indication-01.txt > Pages : 15 > Date : 2008-02-22 > > 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. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-vanelburg-sipping-pr > ivate-network-indication-01.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in > the body of > the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > Internet-Drafts are also available by anonymous FTP. Login with the > username "anonymous" and a password of your e-mail address. After > logging in, type "cd internet-drafts" and then > "get draft-vanelburg-sipping-private-network-indication-01.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE > /internet-drafts/draft-vanelburg-sipping-private-network-indic > ation-01.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant > mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ 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
- Re: [Sipping] I-D Action:draft-vanelburg-sipping-… Elwell, John
- Re: [Sipping] I-D Action:draft-vanelburg-sipping-… Hans Erik van Elburg