Re: [Int-area] IP-in-IP, TTL decrementing when forwarding and BITW

Pekka Savola <pekkas@netcore.fi> Fri, 02 June 2006 18:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmEL3-0004aX-6n; Fri, 02 Jun 2006 14:25:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmEL1-0004Zy-UJ for int-area@ietf.org; Fri, 02 Jun 2006 14:25:35 -0400
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmEKV-0003hr-EQ for int-area@ietf.org; Fri, 02 Jun 2006 14:25:04 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060308/8.12.11) with ESMTP id k52IP07T005696; Fri, 2 Jun 2006 21:25:00 +0300
Date: Fri, 02 Jun 2006 21:25:00 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [Int-area] IP-in-IP, TTL decrementing when forwarding and BITW
In-Reply-To: <4480438F.6030206@isi.edu>
Message-ID: <Pine.LNX.4.64.0606022119490.5484@netcore.fi>
References: <Pine.LNX.4.64.0606020830220.12705@netcore.fi> <4480438F.6030206@isi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.88.2/1505/Thu Jun 1 21:29:37 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: int-area@ietf.org, "Charles E. Perkins" <charliep@iprg.nokia.com>
X-BeenThere: int-area@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/int-area>
List-Post: <mailto:int-area@lists.ietf.org>
List-Help: <mailto:int-area-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@lists.ietf.org?subject=subscribe>
Errors-To: int-area-bounces@lists.ietf.org

(Btw, some people didn't know BITW stands for "Bump in the Wire".)

On Fri, 2 Jun 2006, Joe Touch wrote:
> FWIW, there are two cases I considered where tunnel decrementing might
> not occur:
>
> 	1) BITW
> 		typically this is for IPsec tunnels, which are
> 		spec'd in 4301, but which in spirit ought to follow
> 		2003
>
> 		they might also be used for range-extenders

No disagreement about host-to-host tunnels.

As said, I don't see BITW functionality specified or implied in RFC 
2003.  But I'd like to know what others think.

The reason why I think BITW is not important or even relevant in this 
context is that such "BITW-like behaviour" is better achieved by L2 
tunneling, which at the same time can also be agnostic of the various 
L3 protocols that might need to be "bumped".

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
Int-area mailing list
Int-area@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area