The Interface to the Routing System (I2RS) WG will hold virtual interim
meetings on the following dates:
Date: April 29, 2015
Time: 10:00-11:30 AM EDT (14:00-15:30 UTC)
Topic: I2RS protocol requirements
Date: May 13, 2015
Time: 10:00-11:30 AM EDT (14:00-15:30 UTC)
Topic: Filter-Based RIB
Date:
Himanshu:
Just to make sure I understand your comment, you do not feel an I2RS WG
draft on topology should include a protocol independent virtual topology at
Layer 2. I will bring this comment to the attention of the Routing AD in
charge of the I2RS work.
The L2VPN, BESS, IEEE, PALS document a
I agree with Tom. This work does not seem to applicable to I2RS WG.
At best, it is related to L2VPN WG, now, PALS and BESS.
And in addition, there are other SDOs that are working on this as well.
It would be difficult to unwind the overlap.
/himanshu
-Original Message-
From: i2rs [mailto:
Alia Atlas (our Routing AD) has requested that we move the I2RS interims
from Thursday to Wednesdays. Based on this feedback, we plan to hold the
I2RS interims on these dates at this time.
Date
Time (EDT)
Topic
4/15
10:00 -11:30am
I2RS protocol (alternate protocol proposal)
4/29
1
Mahesh:
Thank you for your input on the MEF L2 Service topologies.
Just to be clear, the I2RS L2 Topology model is simply a virtual topology model
as specified in the I2RS charter. This virtual topology model provides a link
between the Service layer, L3 layer, L2 layer, and the physic
There is a PAR/CSD making its way through dot1Q to develop YANG models in
that committee. The first of those models is to develop the bridge model.
In addition to IEEE, I would think that the L2 topology work would be
better served in MEF where we are trying to develop service models for L2
servic
Tom:
I'll drop a note to official liaison for IEEE is a good idea, and other IEEE
members of 802.1 I know. Thank you for that input.
The I2RS L2 protocol topology is the protocol independent topology. Just as
Alexander Clemm points out that the L3 topology may be a virtual composite
of either
> On Apr 6, 2015:11:17 AM, at 11:17 AM, Juergen Schoenwaelder
> wrote:
>
> On Mon, Apr 06, 2015 at 09:11:39AM -0400, Susan Hares wrote:
>> This begins a 2 week adoption call for
>> draft-dong-i2rs-l2-network-topology-01.
>>
>> Please indicate in your comments "support" or "no support" and dis
On Mon, Apr 06, 2015 at 09:11:39AM -0400, Susan Hares wrote:
> This begins a 2 week adoption call for
> draft-dong-i2rs-l2-network-topology-01.
>
> Please indicate in your comments "support" or "no support" and discuss how
> this draft will allow I2RS client-agent pairs to query information about
Hi Sue
I agree. Recent L2 control planes have leverage common mechanisms such as
routing as well as supporting learning. I think it helps to model based on the
generic model with common terms at L2 and L3.
Cheers,
Don
From: i2rs [mailto:i2rs-boun...@ietf.org] On Behalf Of Susan Hares
Sent: Mon
Tom:
See the charter text from http://datatracker.ietf.org/wg/i2rs/charter/
o The ability to extract information about topology from the network.
Injection and creation of topology will not be considered as a work item. Such
topology-related models will be based on a generic topology mo
Is this currently in the charter or does the charter need to be
extended
to allow for non-RIB related topology models to be included in i2rs? As I
recall,
this is why we didn't do any L1 topology for optical networks, which was
something one particular operator requested at the time but
This begins a 2 week adoption call for
draft-dong-i2rs-l2-network-topology-01.
Please indicate in your comments "support" or "no support" and discuss how
this draft will allow I2RS client-agent pairs to query information about L2
topology. The draft can be found at:
http://datatracker.ie
This begins a 2 week adoption call for draft-clemm-i2rs-yang-l3-topo-00.txt.
Please indicate in your comments "support" or "no support" and discuss how
this draft will allow I2RS client-agent pairs to query information about L3
topology. The draft can be found at:
http://datatracker.ietf.
14 matches
Mail list logo