Re: [OSPF] What is the use of MTU field in DD packet

Paul Wells <pauwells@cisco.com> Wed, 28 May 2008 18:04 UTC

Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E3D33A6B88; Wed, 28 May 2008 11:04:59 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51C028C0DE for <ospf@core3.amsl.com>; Wed, 28 May 2008 11:04:56 -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=[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 SqT1BZ4jM7Qj for <ospf@core3.amsl.com>; Wed, 28 May 2008 11:04:55 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id B87833A6A6D for <ospf@ietf.org>; Wed, 28 May 2008 11:04:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,556,1204531200"; d="scan'208";a="36687752"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 28 May 2008 11:05:04 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4SI54q9031255; Wed, 28 May 2008 11:05:04 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4SI54SG004490; Wed, 28 May 2008 18:05:04 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 May 2008 11:05:04 -0700
Received: from pauwells-linux.cisco.com ([10.19.20.100]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 May 2008 11:05:03 -0700
Message-ID: <483D9ECE.5080300@cisco.com>
Date: Wed, 28 May 2008 13:05:02 -0500
From: Paul Wells <pauwells@cisco.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Acee Lindem <acee@redback.com>
References: <079701c889ec$22702080$0200a8c0@your029b8cecfe> <C71840B5-D198-4EA8-B132-0EFD68F54FD8@redback.com> <FDC03E35ADE75E40946C3E92BE45EA5E01518A42@emailbng2.jnpr.net> <BDF86469-AC88-444C-BABD-A80F4E774A41@redback.com>
In-Reply-To: <BDF86469-AC88-444C-BABD-A80F4E774A41@redback.com>
X-OriginalArrivalTime: 28 May 2008 18:05:03.0873 (UTC) FILETIME=[5A886710:01C8C0ED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1909; t=1211997904; x=1212861904; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pauwells@cisco.com; z=From:=20Paul=20Wells=20<pauwells@cisco.com> |Subject:=20Re=3A=20[OSPF]=20What=20is=20the=20use=20of=20M TU=20field=20in=20DD=20packet |Sender:=20; bh=fQjY8gJP/Q0CWJww7ur62a8dqmntLx+vIdA4LVP6SiI=; b=zXjLv3M/DgqSLQisKSyjWdIozjODAuBY9EoINZfSqk8OSVmCK1bsdze2jU jEMmj/s+XI1fBfglI79ZF8WSwC6zSuRbli8nsVED/VM5k2jRIzcyyPjyUszd UnzmEMUT5u;
Authentication-Results: sj-dkim-2; header.From=pauwells@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] What is the use of MTU field in DD packet
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org

Hi Acee,

I disagree about the "original intent" of the MTU field. As I see 
it, it's function is to prevent an OSPF adjacency from forming 
over a link where the endpoints disagree about the link MTU. We do 
this primarily to prevent the data plane from using a link that 
will drop packets sent to a system with an MTU smaller than ours.

While OSPFv3 certainly needs to know the IPv6 link MTU when 
building it's packets, this information should be available 
locally without reference to the MTU field in the DBD packet.

So, I would argue that in af-alt the MTU in the DBD packet should 
be for the address family we are routing, not IPv6 in all cases.

Regards,
Paul

Acee Lindem wrote:
> Hi Prasanna,
> 
> On May 28, 2008, at 8:18 AM, Prasanna Kumar A.S wrote:
> 
>> Hi
>>   I just wanted to understand what the primary use of exchanging  
>> MTU in
>> DD packets and doing MTU-check is? Is it only for the control plane or
>> is it for the DATA-plane?
> 
> Control-plane - when sending DD, LSR, and LSU packets, OSPF will  
> attempt to send as many LSA headers or complete LSAs as will fit in a  
> maximum sized packet.
> 
> 
>> Why I am getting this doubt is, in draft-ietf-ospf-af-alt-06.txt  
>> doesn't
>> specify which MTU we should use while exchanging the DD packet for the
>> ipv4-unicast or ipv4-mutlticast Address-family, is it ipv6-mtu or
>> ipv4-mtu?
> 
> We have this clarified in the an update which we post soon. Since  
> this is OSPFv3 which using IPv6 for transport, you always use the  
> IPv6 MTU.
> 
> Thanks,
> Acee
> 
> 
>>
>> Regards
>> Prasanna
>> _______________________________________________
>> OSPF mailing list
>> OSPF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ospf
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf