IETF Logo Mail Archive

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

Acee Lindem <acee@redback.com> Wed, 28 May 2008 12:24 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 2D9063A6929; Wed, 28 May 2008 05:24:22 -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 D490B3A6929 for <ospf@core3.amsl.com>; Wed, 28 May 2008 05:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 YgLxay6dHNhP for <ospf@core3.amsl.com>; Wed, 28 May 2008 05:24:18 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id F16143A67C0 for <ospf@ietf.org>; Wed, 28 May 2008 05:24:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id AA2AF6014D1; Wed, 28 May 2008 05:24:22 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13281-02; Wed, 28 May 2008 05:24:22 -0700 (PDT)
Received: from [JC???n?IPv6???1] (login005.redback.com [155.53.12.64]) by prattle.redback.com (Postfix) with ESMTP id DC62941F65F; Wed, 28 May 2008 05:24:08 -0700 (PDT)
In-Reply-To: <FDC03E35ADE75E40946C3E92BE45EA5E01518A42@emailbng2.jnpr.net>
References: <079701c889ec$22702080$0200a8c0@your029b8cecfe> <C71840B5-D198-4EA8-B132-0EFD68F54FD8@redback.com> <FDC03E35ADE75E40946C3E92BE45EA5E01518A42@emailbng2.jnpr.net>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <BDF86469-AC88-444C-BABD-A80F4E774A41@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Wed, 28 May 2008 08:24:07 -0400
To: "Prasanna Kumar A.S" <sprasanna@juniper.net>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
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 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

v2.23.0 | Report a Bug | By Email