RE: draft-ietf-ipngwg-p2p-pingpong-00.txt vs RFC4443

Olivier Vautrin <ovautrin@juniper.net> Tue, 17 August 2010 22:38 UTC

Return-Path: <ovautrin@juniper.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA5153A67F7 for <ipv6@core3.amsl.com>; Tue, 17 Aug 2010 15:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xstV-7jg6kJC for <ipv6@core3.amsl.com>; Tue, 17 Aug 2010 15:38:06 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by core3.amsl.com (Postfix) with ESMTP id EDFD33A6828 for <ipv6@ietf.org>; Tue, 17 Aug 2010 15:38:05 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKTGsPZiEXQCqXJSyOXH2Nu+L+e89JinZr@postini.com; Tue, 17 Aug 2010 15:38:41 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Tue, 17 Aug 2010 15:38:00 -0700
From: Olivier Vautrin <ovautrin@juniper.net>
To: Fernando Gont <fernando@gont.com.ar>, Pekka Savola <pekkas@netcore.fi>
Date: Tue, 17 Aug 2010 15:37:59 -0700
Subject: RE: draft-ietf-ipngwg-p2p-pingpong-00.txt vs RFC4443
Thread-Topic: draft-ietf-ipngwg-p2p-pingpong-00.txt vs RFC4443
Thread-Index: Acs+AwCh3n47dMecQACu+KHr6aNn4wAWYOKQ
Message-ID: <84600D05C20FF943918238042D7670FD36D7088B7B@EMBX01-HQ.jnpr.net>
References: <4C68F1E1.2090003@gont.com.ar> <4C68FD84.80905@unfix.org> <4C6920F8.7010505@gont.com.ar> <84600D05C20FF943918238042D7670FD36D708817A@EMBX01-HQ.jnpr.net> <alpine.LRH.2.00.1008171116150.1433@netcore.fi> <4C6A6C2F.1060409@gont.com.ar>
In-Reply-To: <4C6A6C2F.1060409@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 17 Aug 2010 16:24:57 -0700
Cc: "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Aug 2010 22:38:07 -0000

> 
> > FWIW, "Packet may be forwarded back on the received interface" is
> > actually, AFAIK, used in certain PE routerscenarios where you ping
> > yourself over a p2p link.
> 
> Is the echo request/response really forwarded back on the received
> interface? (isn't the *response* that is forwarded back on the received
> interface?)
> 

No. Again, There could be cases where packet needs to be sent back onto point-to-point links from which they were received.  For example, an LER (Label Edge Router) could just forward the packet solely based on its label without IP resolution.  In this case, if the destination was the LER's egress interface, then the downstream router would do an IP lookup and sent back the packet to its interface (it could be a ping to the LSR egress interface for example).

If the downstream router was using RFC4443, it would break the ping (in this example).

/Olivier