Re: [pcp] TR: I-D Action: draft-boucadair-pcp-sip-ipv6-00.txt

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Tue, 27 August 2013 05:37 UTC

Return-Path: <tireddy@cisco.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDA811E8286 for <pcp@ietfa.amsl.com>; Mon, 26 Aug 2013 22:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELqZmqsPHkNF for <pcp@ietfa.amsl.com>; Mon, 26 Aug 2013 22:37:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD9911E8143 for <pcp@ietf.org>; Mon, 26 Aug 2013 22:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3329; q=dns/txt; s=iport; t=1377581864; x=1378791464; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FfBg4/GXMwTj0pNxBjWHrHX338rRurBU5TR5qvyKmNE=; b=Zul4bwvJUYUD2qk3IhdwBMivCYI/9Cdvv03QNFIKpzSKSj5S6DJJStpx kwKdDtWpKao7FSwdHI4qfIw+wggqLjDPGuxOIRuDcNovsxR2+a9noFf0z PZSDjd7dXcexGdvWmY1QVHfpvhtTuxKQg32a3rzw4010ZZvZ4sk6GG7Hq 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AssGAOQ5HFKtJV2d/2dsb2JhbABagwc1UcAqgSEWbQeCJAEBAQQBAQFrCwwEAgEIEQQBAQsdBycLFAkIAgQOBQgBh3gMuBmQRjECBQaDFn0DiHmQIosLhSmDHoIq
X-IronPort-AV: E=Sophos;i="4.89,965,1367971200"; d="scan'208";a="252011318"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 27 Aug 2013 05:37:43 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r7R5bhKR018788 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Aug 2013 05:37:43 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.8]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Tue, 27 Aug 2013 00:37:43 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [pcp] TR: I-D Action: draft-boucadair-pcp-sip-ipv6-00.txt
Thread-Index: AQHOcp9hX1a06Q1Jd0WrPGbRAngbYpmkB3sQ
Date: Tue, 27 Aug 2013 05:37:42 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A19032570@xmb-rcd-x10.cisco.com>
References: <20130626134028.17581.26454.idtracker@ietfa.amsl.com> <94C682931C08B048B7A8645303FDC9F36EDB5C82CE@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EDB5C82CE@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.54.103]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] TR: I-D Action: draft-boucadair-pcp-sip-ipv6-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 05:37:49 -0000

Hi Med,

comments 

[1] The title is "PCP for IPv6-enabled SIP Deployments" but the draft also discusses problems related to IPv4 networks as well.

[2] can you provide more details on what "managed networks" are considered for this draft (Mobile, Enterprise etc); An example of "managed network" with a diagram will be helpful.

[3] comments on section 2.7

a)
If the SIP server is deployed in the EPC of 3GPP network, SIP server itself can signal the network to prioritize the media streams.
Is setting DSCP values required in such networks ?

b) 
You may want to create a separate draft for DSCP_POLICY and explain How it can used with http://tools.ietf.org/html/draft-ietf-rtcweb-qos-00 which defines default set of DSCP code point values, PCP FLOWDATA option etc. 

[4] 
I guess administrator can change the policy table to prefer IPv4 addresses over IPv6 addresses as discussed in RFC 6724 and you may want to recommend in the draft that in such deployments (sections 3.1, 3.2) it is recommended to have higher precedence for IPv6.

[6] You may also want to add that PCP can also be used to Optimize IPv6 Firewall Keepalives.

[7] If managed networks like Enterprise are considered, technique discussed in http://tools.ietf.org/html/draft-wing-pcp-third-party-authz-00 would be useful.

[8]Referring to the SIP Flow example in https://tools.ietf.org/html/draft-ietf-pcp-nat64-prefix64-04#section-5.2 would be useful.

-Tiru.

> -----Original Message-----
> From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
> Sent: Wednesday, June 26, 2013 8:35 PM
> To: pcp@ietf.org; mmusic@ietf.org; dispatch@ietf.org
> Subject: [pcp] TR: I-D Action: draft-boucadair-pcp-sip-ipv6-00.txt
> 
> Dear all,
> 
> I submitted this short I-D to explain how PCP can be used in IPv6 SIP
> deployments (with a focus on the managed networks case).
> 
> Cheers,
> Med
> 
> -----Message d'origine-----
> De : i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] De
> la part de internet-drafts@ietf.org
> Envoyé : mercredi 26 juin 2013 15:40
> À : i-d-announce@ietf.org
> Objet : I-D Action: draft-boucadair-pcp-sip-ipv6-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title           : PCP for IPv6-enabled SIP Deployments
> 	Author(s)       : Mohamed Boucadair
> 	Filename        : draft-boucadair-pcp-sip-ipv6-00.txt
> 	Pages           : 7
> 	Date            : 2013-06-26
> 
> Abstract:
>    This document discusses how PCP can be used in IPv6-enabled SIP
>    deployments.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-boucadair-pcp-sip-ipv6
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-boucadair-pcp-sip-ipv6-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt