Hi,
the new version uploaded.
https://datatracker.ietf.org/doc/draft-ietf-isis-reverse-metric/
please review.
thanks.
- Naiming
On Jan 24, 2018, at 2:56 PM, Naiming Shen (naiming)
> wrote:
Hi Chris,
Thanks for the comments, please see replies
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 WG of the IETF.
Title : IS-IS Routing with Reverse Metric
Authors : Naiming Shen
Shane Amante
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 WG of the IETF.
Title : IPv6 Source/Destination Routing using IS-IS
Authors : Fred Baker
David
Alia –
Looks fine to me – thanx. I like the fact that the charter now more clearly
allows work which we have yet to anticipate.
If the staunch IPv6 advocates don’t give you grief for overloading “IP” to mean
“IP/IPv6” you won’t get any from me. ☺
Les
From: Alia Atlas
On Wed, Jan 24, 2018 at 6:11 PM, Jeff Tantsura
wrote:
> Wouldn’t L2 reference would be a bit outdated?
>
There has been work from IEEE and from TRILL in the past as well as other
aspects (e.g. RFC 6165, RFC 6326,
RFC 6329, RFC 7176) and - particularly with TRILL
Hi Les,
Thanks for the suggestions! I've modified the paragraph about IS-IS to
read:
"IS-IS is an IGP specified and standardized by ISO through ISO 10589:2002
and additional RFC standards with extensions to support IP that has been
deployed in the Internet for decades. For the IS-IS protocol,
Hi Alia,
+1 on keeping FRR work in RTGWG ;-)
Cheers,
Jeff
From: rtgwg on behalf of Alia Atlas
Date: Tuesday, January 23, 2018 at 09:22
To: , OSPF List
Cc: RTGWG
Subject: early proposed
Wouldn’t L2 reference would be a bit outdated?
Cheers,
Jeff
From: OSPF on behalf of "Les Ginsberg (ginsberg)"
Date: Wednesday, January 24, 2018 at 15:09
To: Stewart Bryant , "Acee Lindem (acee)"
,
It occurred to me after sending this that perhaps a better statement as regards
IS-IS would be:
“LSR’s work is focused on IP/IPv6 and Layer 2 routing…”
though admittedly there isn’t much going on as regards Layer2 and IS-IS at the
moment.
Les
From: Isis-wg
Hi Chris,
Thanks for the comments, please see replies inline,
> On Jan 24, 2018, at 3:32 AM, Christian Hopps wrote:
>
>
> Here are my comments on -08. The most important one would be the M-ISIS
> discrepancy.
>
> - 3.1 " If an IS-IS router is configured to originate a TE
Since a charter only provides a general definition of the work that falls
within the purview of the WG it requires some adjunct to keep track of the
current priorities.
That could be the list of milestones (which OSPF has regularly maintained – but
IS-IS has not) – or it could simply be the
Yes that fixes that.
How about:
s/The following topics are expected to be an initial focus:/ In addition
to ongoing maintenance, the following topics are expected to be an
initial focus:/
I am just concerned that we need not to loose focus on work in progress.
- Stewart
On 24/01/2018
How about:
LSR will coordinate with CCAMP and BIER on their extensions to the LSR IGPs as
applicable to LSV protocol operation and scale.
Thanks,
Acee
From: Isis-wg on behalf of Alia Atlas
Date: Wednesday, January 24, 2018 at 12:42 PM
To: Stewart
Hi Stewart,
Thanks for the quick feedback. Feel free to provide suggestions for text
changes if you have them.
You've certainly written enough charters :-)
Regards,
Alia
On Wed, Jan 24, 2018 at 12:32 PM, Stewart Bryant
wrote:
> Alia,
> I think that this merger is
Here is the proposed charter for the LSR working group
that will be created from the SPF and ISIS working groups.
This is scheduled for internal review for the IESG telechat on February 8.
https://datatracker.ietf.org/doc/charter-ietf-lsr/
The Link-State Routing (LSR) Working Group is chartered
Last I remember was that you had still some holes in the preference rules
you wrote (as in, this thing may loop in this cornercase) but they were
managable by now (i.e. the draft needs minor prunning on too much
flexibility you gave things and then will work) but I'd need to swap my
memory from
Here are my comments on -08. The most important one would be the
M-ISIS
discrepancy.
- 3.1 " If an IS-IS router is configured to originate a TE Default
Metric
sub-TLV for a link, but receives a Reverse Metric TLV from its
neighbor that does not contain a TE Default Metric sub-TLV,
17 matches
Mail list logo