Hi Joel,

This is correct. Legacy devices or devices constrained in resources (think IoT) 
would have a problem to implement ISIS and the full signaling stack. The 
proposed solution requires them only to support LLDP or some other one-hop 
auto-attach protocol. 

Regards,

Dan


> -----Original Message-----
> From: joel jaeggli [mailto:[email protected]]
> Sent: Tuesday, February 16, 2016 8:05 AM
> To: Romascanu, Dan (Dan); [email protected]
> Cc: Unbehagen Jr, Paul E (Paul)
> Subject: Re: [OPSAWG] automatic attachment of applications and services at
> the edge
> 
> Am I correct in understanding that the goal is to not have to implment spb on
> the client device? so this takes the place of an isis implementation that 
> would
> do the signaling per 802.1aq.
> 
> On 2/15/16 7:09 AM, Romascanu, Dan (Dan) wrote:
> > Hi,
> >
> >
> >
> > I would like to draw the attention of the participants in the OPSAWG
> > on an individual submission that I am co-authoring. The problem we are
> > trying to solve is the optimization / minimizing of the amount of
> > configuration that an operator needs to do when new applications
> > require the creation of paths or tunnels in the core network. In order
> > to avoid the reconfiguration of the core or heavy configuration at the
> > edge the proposed method which we call auto-attachment allows for the
> > usage of a protocol running between the end stations and the first
> > (edge) router that adds the information and characteristics of the new
> > path according to the policies or mapping tables of the operators. A
> > first implementation that we have running code for and is deployed is
> > described in
> > https://datatracker.ietf.org/doc/draft-unbehagen-lldp-spb/
> > and uses the Link Layer Discovery Protocol (LLDP) with an IEEE 802.1aq
> > Shortest Path Bridging (SPB) network.
> >
> >
> >
> > Please have a look and let me know if there is interest and/or similar
> > on-going work. If there is enough interest I plan to request a short
> > slot to discuss the idea at the OPSAWG meeting at IETF 95.
> >
> >
> >
> > Thanks and Regards,
> >
> >
> >
> > Dan
> >
> >
> >
> >
> >
> > _______________________________________________
> > OPSAWG mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/opsawg
> >
> 

_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to