Re: [Isis-wg] Confusion in RFC statement
"Tony Li" <tony.li@tony.li> Fri, 12 September 2008 17:09 UTC
Return-Path: <isis-wg-bounces@ietf.org>
X-Original-To: isis-archive@megatron.ietf.org
Delivered-To: ietfarch-isis-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 6E0383A6A1D;
Fri, 12 Sep 2008 10:09:08 -0700 (PDT)
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 833C13A6A1D
for <isis-wg@core3.amsl.com>; Fri, 12 Sep 2008 10:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.733
X-Spam-Level:
X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[AWL=0.865,
BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 E2Vl84M9JVfz for <isis-wg@core3.amsl.com>;
Fri, 12 Sep 2008 10:09:06 -0700 (PDT)
Received: from QMTA09.westchester.pa.mail.comcast.net
(qmta09.westchester.pa.mail.comcast.net [76.96.62.96])
by core3.amsl.com (Postfix) with ESMTP id ACB4C3A688D
for <isis-wg@ietf.org>; Fri, 12 Sep 2008 10:09:02 -0700 (PDT)
Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52])
by QMTA09.westchester.pa.mail.comcast.net with comcast
id Dn9C1a00317dt5G59t9AT5; Fri, 12 Sep 2008 17:09:10 +0000
Received: from TONYLTM9XP ([155.53.41.237])
by OMTA13.westchester.pa.mail.comcast.net with comcast
id Dt8v1a00E570qEr3Zt8yKj; Fri, 12 Sep 2008 17:09:07 +0000
X-Authority-Analysis: v=1.0 c=1 a=CjxXgO3LAAAA:8 a=tfGp9auiaxyOOpuPtpIA:9
a=6vCI97zHp6_Ac6KFrPYA:7 a=I_Nf2JkQlOAK4aljDt3ry8q8GUQA:4
a=lZB815dzVvQA:10
a=gJcimI5xSWUA:10 a=HUpsJ95cfdSgwCkcgdEA:9 a=TmGnpKvnJV2HikxFvT8A:7
a=kIi1G4KPM9G2fVTHqVDj1yutkeQA:4 a=V9aB5C61OLQA:10 a=RCFuj5rSJbkA:10
a=AfD3MYMu9mQA:10
From: "Tony Li" <tony.li@tony.li>
To: <seal_sum@yahoo.co.in>,
<isis-wg@ietf.org>
References: <969086.6290.qm@web8506.mail.in.yahoo.com>
Date: Fri, 12 Sep 2008 10:08:39 -0700
Message-ID: <FED2D56750394436AE1D71E7B0726DA9@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <969086.6290.qm@web8506.mail.in.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-Index: AckUwJJyLcjMME8NRN+SC1dnqjvUigAOTs6g
Cc: hhwsmit@xs4all.nl
Subject: Re: [Isis-wg] Confusion in RFC statement
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>,
<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>,
<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0162318016=="
Sender: isis-wg-bounces@ietf.org
Errors-To: isis-wg-bounces@ietf.org
Hi Sumanta, A prefix is 'injected' into IS-IS when a router inserts the prefix into it's own LSPs, thereby advertising reachability to that prefix. Yes, normally this is achieved by configuration of a prefix as a reachable address, either by running IS-IS on a particular interface, redistributing routes into IS-IS, configuring summary routes, or possibly through other means. The exact configuration steps or automatic mechanisms for injecting routes into IS-IS is, of course, highly implementation dependent. Regards, Tony _____ From: Sumanta Seal [mailto:seal_sum@yahoo.co.in] Sent: Friday, September 12, 2008 3:16 AM To: isis-wg@ietf.org Cc: hhwsmit@xs4all.nl; tony.li@tony.li Subject: Confusion in RFC statement Hello all, I am having some confusion in a statement in RFC 3784 (IS-IS extension for Traffic Engineering). In section 4.1 (The up/down bit, page 8) of the RFC, there is one statement as "The up/down bit SHALL be set to 0 when a prefix is first injected into IS-IS". In this statement, the meaning of injection of a prefix into IS-IS is not clear to me. How can I inject a prefix into IS-IS ? Does this means configuration of a prefix as reachable address in IS-IS router (by configuration of summary address in the IS-IS router) or something else. Please help me out regarding this issue. Thanks, Sumanta _____ Unlimited freedom, unlimited storage. Get <http://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mai l/yahoomail/tools/tools-08.html/> it now
_______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www.ietf.org/mailman/listinfo/isis-wg
- [Isis-wg] Confusion in RFC statement Sumanta Seal
- Re: [Isis-wg] Confusion in RFC statement Tony Li
- Re: [Isis-wg] Confusion in RFC statement Sumanta Seal