Re: [PCN] I-D Action: draft-ietf-pcn-sm-edge-behaviour-11.txt

<Ruediger.Geib@telekom.de> Thu, 05 April 2012 08:04 UTC

Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: pcn@ietfa.amsl.com
Delivered-To: pcn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B739221F8598 for <pcn@ietfa.amsl.com>; Thu, 5 Apr 2012 01:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 JK62FS4uc-F2 for <pcn@ietfa.amsl.com>; Thu, 5 Apr 2012 01:04:59 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 25B2721F87CB for <pcn@ietf.org>; Thu, 5 Apr 2012 01:04:44 -0700 (PDT)
Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 05 Apr 2012 10:03:58 +0200
Received: from HE113657.emea1.cds.t-internal.com (10.134.99.17) by HE110889.emea1.cds.t-internal.com (10.134.92.130) with Microsoft SMTP Server (TLS) id 8.3.245.1; Thu, 5 Apr 2012 10:03:58 +0200
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.136]) by HE113657.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 5 Apr 2012 10:03:58 +0200
From: Ruediger.Geib@telekom.de
To: menth@informatik.uni-tuebingen.de
Date: Thu, 05 Apr 2012 10:03:56 +0200
Thread-Topic: [PCN] I-D Action: draft-ietf-pcn-sm-edge-behaviour-11.txt
Thread-Index: Ac0S+1KSQY2PFizAQdS2qYb0177ddQABi26A
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D13DE980C18@HE111648.emea1.cds.t-internal.com>
References: <20120405003153.32599.76900.idtracker@ietfa.amsl.com> <4F7CF5F4.1010309@gmail.com> <580BEA5E3B99744AB1F5BFF5E9A3C67D13DE980B0E@HE111648.emea1.cds.t-internal.com> <4F7D4597.3060208@informatik.uni-tuebingen.de>
In-Reply-To: <4F7D4597.3060208@informatik.uni-tuebingen.de>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: pcn@ietf.org
Subject: Re: [PCN] I-D Action: draft-ietf-pcn-sm-edge-behaviour-11.txt
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 08:04:59 -0000

Hi Michael,

if public IP traffic is tranported, the pen ultimate hop removes the
last MPLS label. Then there's an IP header below and it must receive the
correct CE codepoint. Tom's issue is something different.

I didn't check whether there are IP-in-IP tunnels which would be
regarded as public instead of VPN. I don't want to invest too much
time, as I prefer an approach working with ECMP and public IP, ie.
no tunnels.

Regards,

Ruediger


-----Original Message-----
From: Michael Menth [mailto:menth@informatik.uni-tuebingen.de]
Sent: Thursday, April 05, 2012 9:11 AM
To: Geib, Rüdiger
Cc: tom.taylor.stds@gmail.com; pcn@ietf.org
Subject: Re: [PCN] I-D Action: draft-ietf-pcn-sm-edge-behaviour-11.txt

Hi Ruediger,

was this the issue with pen-ultimate hop popping? If so, this problem
should be explicitly addressed, otherwise it will be just lost as I am
already now not sure what the background of this text is.

Best wishes,

     Michael

Am 05.04.2012 08:58, schrieb Ruediger.Geib@telekom.de:
> Hi Tom,
>
> thanks. You've requested comments on
>
>
> #######
>
> Section 5.1.2, second paragraph, last sentence
> ----------------------------------------------
>
> OLD
>
> Since all PCN packets will be tunneled, the PCN-ingress-node also needs
> to know the address of the peer PCN-egress-node associated with each filter.
>
> NEW
>
> The PCN-ingress-node also needs to know the address of the next-hop
> PCN-node associated with each filter.
>
> *Comment*: I think I should have added: "If tunneling is used, the
> next-hop PCN-node will be the peer PCN-egress-node."
>
> *Further comment*: how should this read for MPLS?
>
> #########
>
>
> My take is that the tunnel terminates at the PCN-egress-node or at least
> at a node having this functionality. So the next hop as seen from the inner
> (tunneled) packet is the PCN-egress-node.
>
> The next-hop node following the PCN ingress node should have SM PCN marking
> capability, no matter whether it is an IP node or an MPLS node. The next hop
> as seen from the outer (tunnel header) packet is a PCN node.
>
> Regards,
>
> Ruediger
>
>
> Please note that I will be off until 16. April and will not respond to mails before that day.
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

--
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505
fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de
http://kn.inf.uni-tuebingen.de