Naiming Shen | 3 Apr 2005 07:46
Picon
Favicon

Re: I-D ACTION:draft-ietf-isis-wg-multi-topology-09.txt

Dave & Chris,

Can you issue a LC on the draft?

Just want to add here the reasons of the change in the latest
version I mentioned below: on a LAN, if an interface is
configured of running ISIS level-1-2, there is a possibility
that the MT set in L1 IIH is different from the MT set in L2 IIH,
thus it's possible to have two routers on the LAN form different
MT set of adjacency between the L1 and L2.

For example, R1 advertises MT a and MT b in both L1 and L2 IIHs,
but R2 advertises MT a in L1 IIHs, MT a and MT b in L2 IIHs. It
forms a L1/L2 boundary for MT b, but not for MT a.

 From spec point of view, this is nothing wrong. Since each MT
carries it's own ATT bit and each MT calculates it's own
routes, there is no need to make the L1/L2 alignment for all
the MTs. Thus we removed the sentence "boundaries between levels
will be the same for all MTs." in the latest version of the
draft. Thanks to Les who raised this issue.

Although I don't see any reason to make the boundaries differently
for the MTs, as far as I know of, none of the current
implementations allows users configuring MT set differently
for the two levels. But it's an implementation and configuration
choice.

thanks.
- Naiming
(Continue reading)

David Ward | 5 Apr 2005 00:24
Picon
Favicon

Last Call announcement

All -

We are announcing Last Call for:

M-ISIS: Multi Topology (MT) Routing in IS-IS

http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-multi-topology-09.txt

Please submit final comments before April 25th, 2005.

Thanks

Dave and Chris
Parker, Jeff | 11 Apr 2005 21:45
Favicon

Version 19 of Mib

I have just posted version 19 of the MIB to the IETF after our recent MIB Dr
Review.  Change list below.

The largest change was adding a read-only compliance section, which should
not impose an implementation burden.

I'd be happy to unicast a copy of the mib to those who can't wait for it to
appear.  

- jeff parker 

--  Changes in version 19
--
--      Removed restrictions on InetAddress and
--          InetPrefixLength.
--      Removed restriction on which flavors of IP
--          we need to support.
--      Added mib-2 to list of imports.
--      Changed description of isisNextCircIndex
--      Removed comment that Reachable Address Group
--          was optional.
--      Added text about matching IP address to Type, and
--          prefix length to address
--      Added and updated references
--      Added ReadOnly Compliance section
--      Replaced edge-triggered notifications with time-based throttling
--      Added new TC called IsisAdjLevel
--          Revised isisISAdjUsage to use the new TC
Internet-Drafts | 12 Apr 2005 21:38
Picon
Favicon

I-D ACTION:draft-ietf-isis-wg-mib-19.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-19.txt
	Pages		: 99
	Date		: 2005-4-12
	
This document describes a management information base for the IS-IS
   Routing protocol when it is used to construct routing tables for IP
   networks.

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-mib-19.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.

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-wg-mib-19.txt".

A list of Internet-Drafts directories can be found in
(Continue reading)

Mike Bartlett | 13 Apr 2005 12:39
Favicon

Comments on draft-ietf-isis-wg-multi-topology-09

Hello all,

I have just read this draft for the first time and have some comments on it.  Firstly there are two specific
areas where I'm unsure how a router should behave when supporting this draft.  Secondly I have raised some
editorial-type issues including typos.

I'd be grateful for your feedback on the points I have raised.

Many thanks,

Mike Bartlett

-------------------------------------------
Mike Bartlett
Network Protocols Group
Data Connection Ltd
Tel:	+44 20 8366 1177                 
Fax:	+44 20 8363 1039
Email:	mb <at> dataconnection.com    
Web:	http://www.dataconnection.com

Specific issues
---------------

1. Suppose that two routers R1 and R2 are exchanging IIHs over a point-to-point interface.  R1 supports the
MT extensions and only uses MT ID#1 on this interface.  R2 is not including the MT capability TLV at all on its
IIHs.  Should R1 attempt to form an adjacency?  In section 5.1 the specification of what to do seems
contradictory to me.  

There are two conflicting possibilities.  In one case R1 should form an adjacency and in one case it
(Continue reading)

Naiming Shen | 14 Apr 2005 09:35
Picon
Favicon

Re: Comments on draft-ietf-isis-wg-multi-topology-09

Mike,

See some replies inline.

Mike Bartlett said the following on 04/13/2005 03:39 AM:
  ] Hello all,
  ]
  ] I have just read this draft for the first time and have some comments
  ] on it.  Firstly there are two specific areas where I'm unsure how a
  ] router should behave when supporting this draft.  Secondly I have
  ] raised some editorial-type issues including typos.
  ]
  ] I'd be grateful for your feedback on the points I have raised.
  ]
  ] Many thanks,
  ]
  ] Mike Bartlett
  ]
  ] ------------------------------------------- Mike Bartlett Network
  ] Protocols Group Data Connection Ltd Tel:     +44 20 8366 1177
  ]  Fax:        +44 20 8363 1039 Email: mb <at> dataconnection.com Web:
  ] http://www.dataconnection.com
  ]
  ]
  ] Specific issues ---------------
  ]
  ] 1. Suppose that two routers R1 and R2 are exchanging IIHs over a
  ] point-to-point interface.  R1 supports the MT extensions and only
  ] uses MT ID#1 on this interface.  R2 is not including the MT
  ] capability TLV at all on its IIHs.  Should R1 attempt to form an
(Continue reading)

C. M. Heard | 15 Apr 2005 11:08
Picon
Favicon

Mib Doctor review of: draft-ietf-isis-wg-mib-19.txt

On Sun, 6 Mar 2005, C. M. Heard wrote:
> I have done a somewhat cursory review of the most recent version
> which was <draft-ietf-isis-wg-mib-18.txt>.  In general, it appears
> to be technically sound to the extent that I am able to judge (which
> is limited because I know little about IS-IS).  However, there are a
> number of small things that probably should be corrected before the
> document goes to the IESG. The details follow below (organized
> according to the checklist in Appendix A of
> draft-ietf-ops-mib-review-guidelines-04.txt).  The things most
> likely to elicit DISCUSS comments from the IESG are probably 6,
> 10(c), and 10(d).  Note:  please address replies to the WG mailing
> list with copies to Bert Wijnen, Juergen Schoenwaelder, and myself.

I have looked over the latest update <draft-ietf-isis-wg-mib-19.txt>
which was posted on 11 April.  Owing to time constraints I have had
to focus exclusively on how previous review comments were addresses.
My findings are as follows.

> 1.) I-D Boilerplate -- OK

No new issues.

> 2.) Abstract -- some citations are present, which is not allowed (see
> http://www.ietf.org/ID-Checklist.html Section 3(1)C).  In addition,
> since this document is intended for the standards track, please change
> the phrase "an experimental portion" to "a portion" in the 2nd
> paragraph.

Fixed.

(Continue reading)

Parker, Jeff | 15 Apr 2005 16:03
Favicon

Re: Mib Doctor review of: draft-ietf-isis-wg-mib-19.txt

Thanks for the gimlet-eyed review.  I will revise, circulate a draft
privately, and resubmit a new ID shortly.

- jeff parker

On 4/15/05 5:08 AM, "C. M. Heard" <heard <at> pobox.com> wrote:

> I have looked over the latest update <draft-ietf-isis-wg-mib-19.txt>
> which was posted on 11 April.  Owing to time constraints I have had
> to focus exclusively on how previous review comments were addresses.
> My findings are as follows.
> ...

- and -

On 4/15/05 8:36 AM, "Wijnen, Bert (Bert)" <bwijnen <at> lucent.com> wrote:

> Thanks again Mike for your re-review.
> 
> So Jeff, I assume we can expect a quick respind to address
> the remaining (quite containable) remarks/concerns?
> 
> Bert
Wijnen, Bert (Bert | 15 Apr 2005 14:36
Picon
Favicon

RE: Mib Doctor review of: draft-ietf-isis-wg-mib-19.txt

Thanks again Mike for your re-review.

So Jeff, I assume we can expect a quick respind to address 
the remaining (quite containable) remarks/concerns?

Bert

> -----Original Message-----
> From: C. M. Heard [mailto:heard <at> pobox.com]
> Sent: Friday, April 15, 2005 11:09
> To: ISIS WG; Jeff Parker
> Cc: Wijnen, Bert (Bert); Juergen Schoenwaelder
> Subject: Mib Doctor review of: draft-ietf-isis-wg-mib-19.txt
> 
> 
> On Sun, 6 Mar 2005, C. M. Heard wrote:
> > I have done a somewhat cursory review of the most recent version
> > which was <draft-ietf-isis-wg-mib-18.txt>.  In general, it appears
> > to be technically sound to the extent that I am able to judge (which
> > is limited because I know little about IS-IS).  However, there are a
> > number of small things that probably should be corrected before the
> > document goes to the IESG. The details follow below (organized
> > according to the checklist in Appendix A of
> > draft-ietf-ops-mib-review-guidelines-04.txt).  The things most
> > likely to elicit DISCUSS comments from the IESG are probably 6,
> > 10(c), and 10(d).  Note:  please address replies to the WG mailing
> > list with copies to Bert Wijnen, Juergen Schoenwaelder, and myself.
> 
> I have looked over the latest update <draft-ietf-isis-wg-mib-19.txt>
> which was posted on 11 April.  Owing to time constraints I have had
(Continue reading)

Internet-Drafts | 18 Apr 2005 21:52
Picon
Favicon

I-D ACTION:draft-ietf-isis-caps-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		: IS-IS extensions for advertising router information
	Author(s)	: J. Vasseur, et al.
	Filename	: draft-ietf-isis-caps-01.txt
	Pages		: 8
	Date		: 2005-4-18
	
This document defines a new optional IS-IS TLV named CAPABILITY, 
  formed of multiple sub-TLVs, which allows a router to announce its 
  capabilities within an IS-IS level or the entire routing domain.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-caps-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.

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-caps-01.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

(Continue reading)


Gmane