Jeff Parker | 14 Jan 16:37 2004

Encapsulation of larger frames on GigE

Is there agreement on a way to encapsulate large ISO PDUs over GigE?  I see
the following draft, but have no idea how widely this is used.  

http://www.ieee802.org/17/email/msg00388.html

- jeff parker
- axiowave networks
- As scarce as truth is, the supply has always been in excess of the demand
- Josh Billings
Internet-Drafts | 14 Jan 21:54 2004
Picon

I-D ACTION:draft-ietf-isis-restart-05.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		: Restart signaling for IS-IS
	Author(s)	: M. Shand
	Filename	: draft-ietf-isis-restart-05.txt
	Pages		: 21
	Date		: 2004-1-14
	
The IS-IS routing protocol (RFC 1195 [2], ISO/IEC 10589 [3]) is a 
link state intra-domain routing protocol. Normally, when an IS-IS 
router is restarted, temporary disruption of routing occurs due to 
events in both the restarting router and the neighbors of the 
restarting router. 
The router which has been restarted computes its own routes before 
achieving database synchronization with its neighbors. The results 
of this computation are likely to be non-convergent with the routes 
computed by other routers in the area/domain. 
Neighbors of the restarting router detect the restart event and 
cycle their adjacencies with the restarting router through the down 
state. The cycling of the adjacency state causes the neighbors to 
regenerate their LSPs describing the adjacency concerned. This in 
turn causes temporary disruption of routes passing through the 
restarting router. 
In certain scenarios the temporary disruption of the routes is 
highly undesirable. This draft describes mechanisms to avoid or 
minimize the disruption due to both of these causes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-restart-05.txt
(Continue reading)

The IESG | 14 Jan 23:51 2004
Picon

Last Call: 'Restart signaling for IS-IS' to Informational RFC

The IESG has received a request from the IS-IS for IP Internets WG to consider 
the following document:

- 'Restart signaling for IS-IS '
   <draft-ietf-isis-restart-05.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg <at> ietf.org or ietf <at> ietf.org mailing lists by 2004-01-28.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-isis-restart-05.txt
Internet-Drafts | 19 Jan 16:35 2004
Picon

I-D ACTION:draft-ietf-isis-experimental-tlv-02.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		: TLV for Experimental Use
	Author(s)	: P. Christian
	Filename	: draft-ietf-isis-experimental-tlv-02.txt
	Pages		: 6
	Date		: 2004-1-16
	
This document defines a TLV that may be used by any individual, 
company or other organisation for experimental extensions to the
IS-IS routing protocol, and defines the format of the TLV.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-isis-experimental-tlv-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

(Continue reading)

Jeff Parker | 19 Jan 22:44 2004

Version 13 of IS-IS Mib

I have submitted a new version of the IS-IS Mib.  Here is the list of
changes from the change log.

Thanks to Don Goodspeed for compiling the version on several mib compilers.

If anyone needs a copy before the official version is up, I would be happy
to send by private mail.

- jeff parker

--      Clarify how isisSysLevelOverloadState gets it's value
--      Clarify values of isisLSPTLVIndex
--      Address issues from htmllint website
--              http://www.icir.org/fenner/mibs/htmllint/ISIS-MIB.html
--          date specification `200302401200Z' contains an illegal day
--          index element `isisLSPTLVIndex' of row `isisLSPTLVEntry' should
--              be not-accessible in SMIv2 MIB
--          name `isisOriginatingLSPBufferSizeMismatch' longer than 32
--          Add new conformance section that covers all groups
--      Clarify isisSysReceiveLSPBufferSize
--      Fix limits on isisOriginatingBufferSize
--      Changes for Notifications
--              Clarify isisAdjacencyChange
--      Modified ranges for some values
--              LinkStatePDUID from OCTET STRING (SIZE(8)) to (SIZE(0|8)
--              IsisPDUHeader OCTET STRING (SIZE(1..64)) to SIZE(0..64))
--              isisPduLspSize Integer32 (1..2147483647) to (0..2147483647)
--              isisPduOriginatingBufferSize (512..16000) to (0..16000)
--      Removed isisIPRAIndex
--      Add size to isisLSPTLVValue:  SYNTAX OCTET STRING (SIZE(0..255))
(Continue reading)

Internet-Drafts | 20 Jan 21:44 2004
Picon

I-D ACTION:draft-ietf-isis-wg-mib-13.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		: Management Information Base for IS-IS
	Author(s)	: J. Parker
	Filename	: draft-ietf-isis-wg-mib-13.txt
	Pages		: 92
	Date		: 2004-1-20
	
This document describes a management information base for the IS-IS
Routing protocol, as described in ISO 10589 [2], when it is used to
construct routing tables for IP networks, as described in RFC 1195
[RFC1195].
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet community.
This memo is based on an IETF draft by Chris Gunner [1].  This
version has been modified to include MIB-II syntax, to exclude
portions of the protocol that are not relevant to IP, such as the
ES-IS protocol, and to add management support for current practice.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
(Continue reading)

Jon Berger | 30 Jan 17:05 2004

draft-ietf-isis-gmpls-extensions-19.txt and unnumbered links

Hello Kireeti, Yakov (and everyone else),

I have the following comments to make on
draft-ietf-isis-gmpls-extensions-19.txt.  My key concerns are in the area of
unnumbered links.

1.	Regarding the Link Local/Remote sub-TLV:
----------------------------------------------

In sections 3.2 and 3.3 (regarding local and remote interface addresses) of
the soon-to-be-RFCed draft-ietf-isis-traffic-05.txt, the following text
appears:

"If a router implements traffic engineering, it MUST include this sub-TLV."

I do not believe this to be true, as unnumbered links will use the Link
Local/Remote ID sub-TLV to identify a link's endpoints, rather than IP
addresses.

Since we cannot change the Traffic Engineering RFC(?), I would like to add a
comment similar to the following to section 1.1 of
draft-ietf-isis-gmpls-extensions-19.txt:

"For unnumbered links, the Link Local/Remote Identifiers sub-TLV is used to
identify a link.  For numbered links the IPv4 interface address and IPv4
neighbor address sub-TLVs are used to identify a link.  For each link only
one set of sub-TLVs should be present."

2.	Again, regarding the Link Local/Remote ID sub-TLV:
--------------------------------------------------------
(Continue reading)


Gmane