headers
Internet-Drafts | 8 Feb 2008 12:15
Picon
Favicon

I-D Action:draft-ietf-isis-rfc2966bis-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title           : Domain-wide Prefix Distribution with Two-Level IS-IS
	Author(s)       : T. Li, et al.
	Filename        : draft-ietf-isis-rfc2966bis-00.txt
	Pages           : 15
	Date            : 2008-02-07

This document describes extensions to the Intermediate System to
Intermediate System (IS-IS) protocol to support optimal routing
within a two-level domain.  The IS-IS protocol is specified in ISO
10589, with extensions for supporting IPv4 (Internet Protocol)
specified in RFC 1195.
This document extends the semantics presented in RFC 1195 so that a
routing domain running with both level 1 and level 2 Intermediate
Systems (IS) [routers] can distribute IP prefixes between level 1 and
level 2 and vice versa.  This distribution requires certain
restrictions to insure that persistent forwarding loops do not form.
The goal of this domain-wide prefix distribution is to increase the
granularity of the routing information within the domain.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-rfc2966bis-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 9 Feb 2008 02:23
Favicon

RFC 5120 on M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5120

        Title:      M-ISIS: Multi Topology (MT) Routing 
                    in Intermediate System to Intermediate Systems 
                    (IS-ISs) 
        Author:     T. Przygienda, N. Shen,
                    N. Sheth
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    prz <at> net4u.ch, 
                    naiming <at> cisco.com, 
                    nsheth <at> juniper.net
        Pages:      14
        Characters: 30318
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-wg-multi-topology-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5120.txt

This document describes an optional mechanism within Intermediate
System to Intermediate Systems (IS-ISs) used today
by many ISPs for IGP routing within their clouds.  This document
describes how to run, within a single IS-IS domain, a set of
independent IP topologies that we call Multi-Topologies (MTs).
This MT extension can be used for a variety of purposes, such as an
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 10 Feb 2008 21:45
Picon
Favicon

I-D Action:draft-ietf-isis-rfc2966bis-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title           : Domain-wide Prefix Distribution with Two-Level IS-IS
	Author(s)       : T. Li, et al.
	Filename        : draft-ietf-isis-rfc2966bis-01.txt
	Pages           : 15
	Date            : 2008-02-09

This document describes extensions to the Intermediate System to
Intermediate System (IS-IS) protocol to support optimal routing
within a two-level domain.  The IS-IS protocol is specified in ISO
10589, with extensions for supporting IPv4 (Internet Protocol)
specified in RFC 1195.
This document extends the semantics presented in RFC 1195 so that a
routing domain running with both level 1 and level 2 Intermediate
Systems (IS) [routers] can distribute IP prefixes between level 1 and
level 2 and vice versa.  This distribution requires certain
restrictions to insure that persistent forwarding loops do not form.
The goal of this domain-wide prefix distribution is to increase the
granularity of the routing information within the domain.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-rfc2966bis-01.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 12 Feb 2008 20:59
Favicon

RFC 5130 on A Policy Control Mechanism in IS-IS Using Administrative Tags


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5130

        Title:      A Policy Control Mechanism in 
                    IS-IS Using Administrative Tags 
        Author:     S. Previdi, M. Shand, Ed.,
                    C. Martin
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    sprevidi <at> cisco.com, 
                    mshand <at> cisco.com, 
                    chris <at> ipath.net
        Pages:      8
        Characters: 16284
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-admin-tags-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5130.txt

This document describes an extension to the IS-IS protocol to add
operational capabilities that allow for ease of management and
control over IP prefix distribution within an IS-IS domain.  This
document enhances the IS-IS protocol by extending the information
that an Intermediate System (IS) router can place in Link State
Protocol (LSP) Data Units for policy use.  This extension will
provide operators with a mechanism to control IP prefix distribution
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 14 Feb 2008 19:37
Picon
Favicon

Protocol Action: 'Routing IPv6 with IS-IS' to Proposed Standard

The IESG has approved the following document:

- 'Routing IPv6 with IS-IS '
   <draft-ietf-isis-ipv6-07.txt> as a Proposed Standard

This document is the product of the IS-IS for IP Internets Working Group. 

The IESG contact persons are Ross Callon and David Ward.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-ipv6-07.txt

Technical Summary

   This draft specifies a method for exchanging IPv6 routing information
   using the IS-IS routing protocol.  The described method utilizes 2
   new TLVs, a reachability TLV and an interface address TLV to
   distribute the necessary IPv6 information throughout a routing
   domain.  Using this method one can route IPv6 along with IPv4 and OSI
   using a single intra-domain routing protocol.

Working Group Summary

 The document is a product of substantial discussion and review within
 the WG, which had strong consensus for putting this document on STD track.

Protocol Quality

 The specification has been reviewed for IESG by Alex Zinin and Bill Fenner.
 There are multiple interoperable implementations of this document.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 18 Feb 2008 18:15
Picon
Favicon

I-D Action:draft-ietf-isis-mi-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title           : IS-IS Multi-Instance
	Author(s)       : S. Previdi, et al.
	Filename        : draft-ietf-isis-mi-00.txt
	Pages           : 9
	Date            : 2008-02-18

This draft describes a mechanism that allows a single router to share
one or more links among multiple IS-IS routing protocol instances.

Multiple instances allow the isolation of resources associated with
each instance.  Routers will form instance specific adjacencies,
exchange instance specific routing updates and compute paths
utilizing instance specific LSDB information.  Each PDU will contain
a new TLV identifying the instance to which the PDU belongs.  This
allows a network operator to deploy multiple IS-IS instances in
parallel, using the same set of links when required and still have
the capability of computing instance specific paths.  This draft does
not address the forwarding paradigm that needs to be used in order to
ensure data PDUs are forwarded according to the paths computed by a
specific instance.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-mi-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Vishwas Manral | 18 Feb 2008 18:41
Favicon

Re: I-D Action:draft-ietf-isis-mi-00.txt

Hi,

I looked at the idea of the draft. Though we say it will work fine with 
older IS-IS implementations which do not support this functionality. I 
guess we need all instances on a network to support it before we can 
turn on the functionality on a network.

Unlike in OSPF, where a use of the functionality without all routers 
supporting it will result in adjacencies not being formed at all.

Thanks,
Vishwas

Internet-Drafts <at> ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.
>
>
> 	Title           : IS-IS Multi-Instance
> 	Author(s)       : S. Previdi, et al.
> 	Filename        : draft-ietf-isis-mi-00.txt
> 	Pages           : 9
> 	Date            : 2008-02-18
>
> This draft describes a mechanism that allows a single router to share
> one or more links among multiple IS-IS routing protocol instances.
>
> Multiple instances allow the isolation of resources associated with
> each instance.  Routers will form instance specific adjacencies,
> exchange instance specific routing updates and compute paths
(Continue reading)

Permalink | Reply | 1 comment |
headers
Les Ginsberg (ginsberg | 18 Feb 2008 19:16
Picon
Favicon

Re: I-D Action:draft-ietf-isis-mi-00.txt

Vishwas -

> -----Original Message-----
> From: isis-wg-bounces <at> ietf.org [mailto:isis-wg-bounces <at> ietf.org] On
Behalf
> Of Vishwas Manral
> Sent: Monday, February 18, 2008 9:41 AM
> Cc: isis-wg <at> ietf.org
> Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-mi-00.txt
> 
> Hi,
> 
> I looked at the idea of the draft. Though we say it will work fine
with
> older IS-IS implementations which do not support this functionality. I
> guess we need all instances on a network to support it before we can
> turn on the functionality on a network.
> 

I am having trouble understanding the concern behind your comment.

Let's suppose we get to a point where all routers support the MI
extension. They still have to be configured to support a particular
instance (say #10) on a set of interfaces. If all the configuration for
instance #10 is not present, the topology will be less than what is
desired. How does this differ from the case where some routers don't
support MI at all?

This isn't a tool to provide automatic configuration.
(Continue reading)

Permalink | Reply | 0 comments |
headers
mike shand | 26 Feb 2008 14:21
Picon
Favicon

draft-isis-pseudo-perlman-roy-thomas-00.txt

I am still not convinced that the mechanism proposed in this draft is a
good idea.

1. As I have said before, we already have the capability to describe a 2
node pt-pt "LAN" as pt-pt links, which not only removes the pseudonode,
but uses the pt-pt update process, no DR election etc. This is a manual
configuration, but I believe that is a benefit since it warns when a
third router is accidentally connected to what is supposed to be a pt-pt
LAN.

2. The proposed mechanism with hysteresis means that the representation
of the network is non-deterministic. i.e. the way the network looks
depends on its previous history.

3. Current network management tools which display the topology will be
unable to distinguish between a 3 node LAN and 3 nodes linked by pt to
pt links. This is exacerbated by the non-determinism.

4. The representation of a 3 node LAN as 3 separate pt-pt links may lead
bandwidth sensitive routing (e.g. the cSPF of MPLS TE) to make wrong
decisions. This is because the single interface onto the LAN will appear
in the link state database as two independent links.

5. The mechanism actually results in an increase in the number of LSPs
which need to be flooded as nodes are attached and removed from the LAN.

Consider the normal case. Going from 2 to 3, 3 to 4, 4 to 3 and 3 to 2
nodes requires 2, 2, 2 & 2 new LSPs respectively. i.e. in each case the
new LSP of the attached/detached node, and a new version of the
pseudonode LSP.
(Continue reading)

Permalink | Reply | 11 comments |
headers
Christian Hopps | 26 Feb 2008 16:07

WG Last Call for draft-ietf-isis-wg-extlsp-02.txt

Hi Folks,

The WG chairs are starting a WG Last Call on the following draft. The  
LC is set to expire the Monday after IETF (March 17th, 2008):

Simplified Extension of LSP Space for IS-IS
<http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-extlsp-02.txt>

Thanks,
Chris & Dave.
Permalink | Reply | 0 comments |

Gmane