[Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop field

"Rohan Sen" <senrohan@gmail.com> Tue, 29 April 2008 18:59 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from core3.amsl.com (localhost []) by core3.amsl.com (Postfix) with ESMTP id ACCF73A6B52; Tue, 29 Apr 2008 11:59:07 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 4F8F23A69F3 for <idr@core3.amsl.com>; Tue, 29 Apr 2008 11:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 91U9hCmPWlVm for <idr@core3.amsl.com>; Tue, 29 Apr 2008 11:59:00 -0700 (PDT)
Received: from ti-out-0910.google.com (ti-out-0910.google.com []) by core3.amsl.com (Postfix) with ESMTP id 1F7503A6B52 for <idr@ietf.org>; Tue, 29 Apr 2008 11:58:59 -0700 (PDT)
Received: by ti-out-0910.google.com with SMTP id i7so51221tid.25 for <idr@ietf.org>; Tue, 29 Apr 2008 11:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=zy+3JlvYPdXv7oAXZ6X4RTUNwpnbRAZLgqgJ9Y/Q0PM=; b=YWSH0mFZ2NCL6wmBYzyP56RIhpJUfk0rid/ZHhSc/6RwyzWo9xC7Rbe8+cJQ26utSrZORuV5rnNC4Jc1amDWTPNjkpRs4t6WGdjsxFIvSdGp9uc3x89A2seBDGRzGFPFMpjN+qoS0TqoGDBPYSUKORKKBn8e0T17jiO8Cvtyi8c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=ddvX84YEz0fnB6lCGLBIt5nG8TBGz6sYsTyRyOs2Fhug/YdL0Rw7cseOOaeVkWejFkfruAcuYck9tTUYzhvbEHGXduCL2aECpNvGNWQ1k8I948gJlvfYVCbGVIHnxU2U3Vit3SDjO75U1nkKxCue6DXSg/t7DajWoviWGh14cKE=
Received: by with SMTP id 17mr905081tit.48.1209495542603; Tue, 29 Apr 2008 11:59:02 -0700 (PDT)
Received: by with HTTP; Tue, 29 Apr 2008 11:59:02 -0700 (PDT)
Message-ID: <8320074d0804291159i7409cdcbn61d9889564becd86@mail.gmail.com>
Date: Wed, 30 Apr 2008 00:29:02 +0530
From: Rohan Sen <senrohan@gmail.com>
To: idr@ietf.org
MIME-Version: 1.0
Subject: [Idr] BGP Next Hop attribute and MP_REACH_NLRI next hop field
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0709888116=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi All,

For cases in BGP (like VPN) where MP_REACH_NLRI attribute is used to carry
route information in an Update message, we also specify the next hop for the
prefixes inside this attribute itself. But if we are sending IPv4 routes
inside MP_REACH_NLRI->NLRI field, and we also add the standard Next Hop path
attribute then will that carry any special meaning? My confusion is that
whether the NLRI path attribute can coexist with MP_REACH_NLRI attribute or
not. If yes, then in which scenario.

Any help in this regard would be highly appreciated.

Rohan Sen
Idr mailing list