Содержание


НазваниеСодержание
страница14/32
ТипДокументы
filling-form.ru > Договоры > Документы
1   ...   10   11   12   13   14   15   16   17   ...   32

MPLS

 

3,347

Is MPLS forwarding supported according to RFC 3031?

Comply

3,348

Is explicit null label and implicit null label supported?
What the default behaviour ?
Is it configurable ?

Comply

3,349

Is MPLS frame format compliant to RFCs 3032 & 4182?

Comply

3,350

Is the equipment able to push, swap and pop MPLS labels?

Comply

3,351

Is it possible to change the interface MTU for MPLS packets?

Comply

3,352

Is it possible to modify TTL processing (change between one mode to another) ?

Comply

3,353

Is it possible to have a different TTL processing for transit packets & local packets

Comply

3,354

If pipe/shortpipe supported, is it possible to fix manually the TTL value imposed ?

Comply

3,355

Is TTL Processing consistent with RFC3443? Please indicate the supported modes in comments (Uniform, short pipe, pipe).

Comply

3,356

Do you support IPFRR (LFA / remote LFA) in combination with LDP to protect LDP LSPs?

Comply

3,357

Does your implementation provide some CLI "show" commands to check FIB and LFIB at RP level and Linecard level ?

Comply

3,358

Is it possible to enable ECMP for MPLS flows? Please detail the hashing algorithm and if the hashing can be tuned.

Comply

3,359

Do you support the LSR MIB in compliance with RFC 3813? If no is there a proprietary MIB?

Comply

3,360

Do you support the FTN MIB in compliance with RFC 3814? If no is there a proprietary MIB?

Partial Comply

3,361

Is P2MP MPLS forwarding (MPLS traffic replication = Branch LSR function) supported in compliance with RFC 4461?

Comply

3,362

Do you support at least 8 replications per P2MP LSP (=fan-out)? Please give the maximum number of P2MP LSP replication supported.

Comply

3,363

Can your implementation act as both Transit and Leaf LSR for a given LSP (= Bud LSR function) in compliance with RFC 4461? Please indicate if there is a hardware requirement for this specific feature

Comply

3,364

Is Label Distribution Protocol implementation compliant with RFC5036?

Comply

3,365

Are extended discovery and targeted sessions implemented according to RFC5036 specification?

Comply

3,366

"Per Interface" & "Per platform" label space supported according to RFC5036 specification?

Partiallly Comply

3,367

Are both "liberal" and "conservation" label retention modes supported according to RFC5036 specification?

Comply

3,368

Can any loopback interface be used as a LDP session identifier?

Comply

3,369

Is LDP-IGP synchronization supported according to RFC5443 and RFC6138 for ISIS protocol" ?

Comply

3,370

Can BGP use LDP LSP to resolve nexthop ?

Comply

3,371

Does a targeted session only carry label mapping information regarding the FEC128 and the FEC129?

Comply

3,372

Does your implementation allow applying a label distribution access list to one LDP session? Please elaborate on the possible terms of this access list.

Comply

3,373

Is it possible to disable penultimate hop popping (i.e. deactivate the advertisement of the implicit null label on the egress-LER)?

Comply

3,374

Do you support static label allocation?

Comply

3,375

Is LDP MD5 signature supported?

Comply

3,376

Is it possible to restrict the set of LDP neighbours using an access list?

Comply

3,377

Is it possible to set up LDP sessions over TE-LSPs (LSPs established by RSVP-TE)?

Comply

3,378

Is LDP graceful restart supported in compliance with RFC3478? If so, please give the default timer values and the range values for each parameter.

Comply

3,379

Are LDP Capabilities supported in compliance with RFC5561?

Partial Comply

3,380

The device must implement "Multi-Protocol Label Switching (MPLS) Support of Differentiated Services" according to RfC 3270.

Comply

3,381

The device should implement the MPLS Generic Associated Channel according to RfC 5586.

Partial Comply

3,382

If the device implements "MPLS Generic Associated Channel" according to RfC 5586, then the vendor must state any 'optional' or 'should' requirements that their implementation does not support.

Partial Comply

3,383

If the device implements "Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)" according to RfC 4023, then the vendor must state any 'optional' or 'should' requirements that their implementation does not support.

Comply

3,384

The vendor must state whether the device implements "Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)" according to RfC 4576.

Comply

3,385

If the device implements "Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)" according to RfC 4576, then the vendor must state any 'optional' or 'should' requirements that their implementation does not support.

Comply

3,386

The vendor must state whether the device implements "OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)" according to RfC 4577.

Comply

3,387

If the device implements "OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)" according to RfC 4577, then the vendor must state any 'optional' or 'should' requirements that their implementation does not support.

Comply

3,388

The vendor must describe administrative controls for BGP/MPLS Layer 3 IPv4 VPNs.

Comply

3,389

The vendor must speciffy if there are limitations (equipment and management system) in using some Route Targets values/ranges

Comply

3,390

The device must support the ability to create an OAM Service VPN, that allows for management of all external interfaces and for import of the selected Route Targets (hub and spoke) for Management and VPN Topology generation purposes.

Comply

3,391

The device must support by default the segregation of Traffic including routing protocol traffic between VPNs.

Comply

3,392

The device must support configuration of MPLS IPv4 VPNs with the same or overlapping IP address spaces.

Comply

3,393

The device must support functionality that prevents visibility of the internal address and network structure of the core network (MPLS PE and P elements).

Comply

3,394

The device must prohibit traffic flowing from customer VPNs to management VPN ports.

Comply

3,395

The device must support that Any VPN can use the same address space as the underlying infrastructure.

Comply

3,396

The device must never accept a packet with a label received from a CE router. Packets containing a label that arrive on a CE interface must be dropped. Thus it is not possible to insert fake labels, because no labels at all are accepted. It must be impossible to send packets with wrong labels from a CE router (the “outside”) through a PE into the MPLS cloud.
1   ...   10   11   12   13   14   15   16   17   ...   32

Похожие:

Содержание iconСодержание содержание 1
Пояснительные записки, тематическое планирование и тексты учебных пособий Летней физико-математической школы. 2002 и 2003 гг

Содержание icon5410611008 нижневартовск 2013 содержание
Общие требования к первой (предквалификационной) и второй частям заявок (содержание, оформление, подача, изменение, отзыв) 15

Содержание icon5182012014 нижневартовск 2013 содержание
Общие требования к первой (предквалификационной) и второй частям заявок (содержание, оформление, подача, изменение, отзыв) 15

Содержание iconПамятка для родителей, имеющих право на муниципальные льготы за содержание...
В соответствии с решением Совета депутатов г. Мурманска от 26. 12. 2006 года №30-357 «Об организации дошкольного образования и родительской...

Содержание iconПамятка для родителей, имеющих право на муниципальные льготы за содержание...
В соответствии с решением Совета депутатов г. Мурманска от 26. 12. 2006 года №30-357 «Об организации дошкольного образования и родительской...

Содержание iconПравила оформления заявки на грант содержание заявки
Научное содержание нир, оформленное по образцу научной публикации (объемом до 15 машинописных страниц, через 1,5 интервала)

Содержание iconКурсовая работа тема: «Содержание договора и классификация его условий»
Неправильное составление договора или неполное содержание влечёт за собой проблемы различного характера

Содержание iconФормата Передачи Данных TransUnion (tutdf) январь 2016 г. Версия 03r Содержание Содержание 2
Разъяснения по выгрузке информации о прекращении банковской гарантии в иных, отличных от окончания срока гарантии случаях. 145

Содержание icon«Актуальные проблемы международного морского права»
Характеристики, структура и содержание Раздел Характеристики, структура и содержание учебной дисциплины

Содержание iconКонспект лекций Тема Сущность, содержание и цели маркетинговой деятельности
Суть и содержание понятия «маркетинг». Цели, задачи, объект и предмет маркетинга. Эволюция содержания маркетинга

Вы можете разместить ссылку на наш сайт:


Все бланки и формы на filling-form.ru




При копировании материала укажите ссылку © 2019
контакты
filling-form.ru

Поиск