[L3sm] 回复: Re: Next steps with L3SM

[赵婧 <[e-mail]>]

Hi,
 So your idea is to represent dual home scenarios with two sites:
   <site-id>Hub#1-PrimarySite</site-id>
   <availability>
       <availability-type>
       <service-type>primary-backup</service-type>
       <access-type>primary</access-type>
   </availability-type>
   </availability>
      <site-id>Hub#1-BackupSite</site-id>
   <availability>
       <availability-type>
       <service-type>primary-backup</service-type>
       <access-type>backup</access-type>
   </availability-type>
   </availability>
That works for me. 
 


JingZhao
 
发件人： [e-mail]
发送时间： 2015-05-12 15:31
收件人： 赵婧
抄送： [e-mail]
主题： Re: [L3sm] Next steps with L3SM
Hi,
 
I think there is a misunderstanding of what a site is here, we consider a site has an access. So Hub#1 will be composed of two sites : one primary and one backup.
 
Best Regards,
 
From: 赵婧 [mailto:[e-mail]] 
Sent: Tuesday, May 12, 2015 05:14
To: LITKOWSKI Stephane SCE/IBNF
Cc: [e-mail]
Subject: RE: [L3sm] Next steps with L3SM
 
Hi, 
1.  In the schema tree, access-type is within availability. Access-type leaf or access-type leaf list? Can dual home site support both primary access and backup access at the same time
[SLI] I don’t see the use case for this, could you elaborate ?
 
How about dual homing case where one hub#1 site has two primary-backup accesses (see the first figure in the section 5.2.1.2):
One is CE1- PE1 primary access, the other is CE2-PE2 backup access, then hub#1 site support dual homing
can be represented as follows:
   <site-id>Hub#1Site</site-id>
   <availability>
       <availability-type>
       <service-type>primary-backup</service-type>
       <access-type>primary</access-type>
       <service-type>primary-backup</service-type>
       <access-type>backup</access-type>
   </availability-type>
   </availability>
So I am wondering whether <availability-type> can be defined as list rather than container? What do you think of this?
Also I am not sure the second figure in the section 5.2.1.2 is wrong or not:
                               Hub#2 LAN
              loadsharing        |
              loadsharing-access |
           PE3 --------- CE3 --- |
                                 |
                                 |
           PE4 --------- CE4 --- |
           |   loadsharing       |
           |   loadsharing-access
           |
           | single
           | single-access
           | loadsharing-eibgp
           |
           CE6
           |
       Spoke#2 site
 
Since it looks to me Spoke# site support single access between PE4 and CE6, but it looks access between PE4 and CE6 also support loadsharing-eibgp, is this intentional? 
 


Jingzhao
Shanghai Research Institution of China Telecom
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.