Can this information be included in the draft?

-----Original Message-----
From: Xuxiaohu [mailto:[email protected]] 
Sent: Thursday, October 23, 2014 1:07 PM
To: S, Somasundaram (Somasundaram); [email protected]
Subject: RE: [bess] I-D Action: draft-ietf-l3vpn-virtual-subnet-02.txt


> -----Original Message-----
> From: S, Somasundaram (Somasundaram)
> [mailto:[email protected]]
> Sent: Thursday, October 23, 2014 3:32 PM
> To: Xuxiaohu; [email protected]
> Subject: RE: [bess] I-D Action: draft-ietf-l3vpn-virtual-subnet-02.txt
> 
> Hi Xu, Do you mean to say that "hosts for which arp is learnt will 
> have to redistributed to BGP" and that BGP implementation will have to 
> take care of this support (through some policy or do it automatically)?

Exactly.

Best regards,
Xiaohu

> Regards
> Somasundaram
> 
> -----Original Message-----
> From: Xuxiaohu [mailto:[email protected]]
> Sent: Thursday, October 23, 2014 12:43 PM
> To: S, Somasundaram (Somasundaram); [email protected]
> Subject: RE: [bess] I-D Action: draft-ietf-l3vpn-virtual-subnet-02.txt
> 
> Hi Somasundaram,
> 
> Those locally connected /32 host routes are redistributed into BGP. 
> It's an implementation issue.
> 
> Best regards,
> Xiaohu
> 
> > -----Original Message-----
> > From: BESS [mailto:[email protected]] On Behalf Of S, 
> > Somasundaram
> > (Somasundaram)
> > Sent: Thursday, October 23, 2014 12:08 PM
> > To: [email protected]
> > Subject: Re: [bess] I-D Action: 
> > draft-ietf-l3vpn-virtual-subnet-02.txt
> >
> > Hello Authors,
> >
> >
> >      I understand that the /32 routes (host routes) are locally 
> > maintained by the routers after ARP resolution. But how is that 
> > exported
> through BGP?
> >
> >    Referring to vrf_A on PE1 of Figure 2) how is 1.1.1.3/32 learnt 
> > over BGP.? I need a better clarity here...
> >
> > Regards
> > Somasundaram
> >
> > -----Original Message-----
> > From: BESS [mailto:[email protected]] On Behalf Of 
> > [email protected]
> > Sent: Thursday, October 23, 2014 8:33 AM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: [bess] I-D Action: draft-ietf-l3vpn-virtual-subnet-02.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> >  This draft is a work item of the BGP Enabled Services Working Group 
> > of the IETF.
> >
> >         Title           : Virtual Subnet: A L3VPN-based Subnet Extension
> > Solution
> >         Authors         : Xiaohu Xu
> >                           Robert Raszuk
> >                           Susan Hares
> >                           Yongbing Fan
> >                           Christian Jacquenet
> >                           Truman Boyes
> >                           Brendan Fee
> >     Filename        : draft-ietf-l3vpn-virtual-subnet-02.txt
> >     Pages           : 14
> >     Date            : 2014-10-22
> >
> > Abstract:
> >    This document describes a Layer3 Virtual Private Network (L3VPN)-
> >    based subnet extension solution referred to as Virtual Subnet, which
> >    can be used for building Layer3 network virtualization overlays
> >    within and/or across data centers.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-l3vpn-virtual-subnet/
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-l3vpn-virtual-subnet-02
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-ietf-l3vpn-virtual-subnet-02
> >
> >
> > Please note that it may take a couple of minutes from the time of 
> > submission until the htmlized version and diff are available at 
> > tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > BESS mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/bess
> >
> > _______________________________________________
> > BESS mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/bess

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

Reply via email to