Shiro ADSL 2/2+ Ethernet Modem Manual de usuario Pagina 579
- Pagina / 638
- Tabla de contenidos
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
)*+,,*
-./
!
))0+)01++,
=!
)(+
42!
*,20
STLF-NA-TRD-REQ-2630 The key identifiers negotiated during the sign-on phase, shall as minimum
deliver:
· or one key for the unicast stream and one key for several (or even all)
multicast services
· one key for the unicast stream and one key per multicast service
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2640 The security signaling protocol composed by security MAC messages are
defined in the DVB-RCS framework. The transport of security messages over
IP using the same protocol stack as the traffic and management planes. Two
pairs of requests/response messages are defined, one aiming at negotiating
security parameters, the other allowing to agree on session keys as well as to
authenticate RCSTs. The following table details the roles played by each pair
of messages: Requests messages are sent by the NCC to the RCSTs and
response messages are sent by the RCSTs to the NCC.
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2650 The security messages over the return path shall be transported using DULM
(section 6.6.2 of [ref DVB RCS]
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2660 The security messages over the forward path shall be transported using a
well known PID.
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2670 As transport mechanism for security messages UDP could be selected. This
avoid the usage of DULM or specific PVC, coherent with IP management
stack, and assured the ability to group several security messages in the
same UDP packet allowing better use of satellite bandwidth
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2680 The security solution shall be compliant with security part 9.4 of [9]. T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2690 The authenticity of the RCST shall be checked by the NCC during the key
exchange step and during a re-keying procedure
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2700 During logon, the RCST shall indicate its encryption/security capability to the
NCC on the CSC burst (RCST Capability field) and the NCC shall
communicate on the logon initialise descriptor whether security shall be
used.
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2710 If security is used, the NCC shall then start the security connection procedure
with the negotiation step by sending as many Sign On request messages as
the data streams required by the RCST
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2720 For Sign On request messages related to multicast forward MPE streams,
the NCC shall select only one encryption algorithm in its proposal, as the
cryptographic context shall be shared by all the RCSTs of the network
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
STLF-NA-TRD-REQ-2730 The RCST shall then reply to each message issuing a Sign On response
message including its choices.
T STLF_IF_RCST_MGMT_AUTH STLF_IO_SEC_RCST
STLF_IO_SEC_RSGW
- 1
- :32-<- 2
- = =:<- :32 2
- <33 3
- --3 10
- 66-*<3 11
- 19
- & ' > - 26
- +0 30
- )0 31
- RTSP/1.0 200 OK 32
- CSeq: 11221 32
- Session: 1121338655 32
- ,=2/> 84
- 126
- )*+,,* 162
- -./ 162
- ))0+)01++ 162
- )10 162
- )20 169
- & 4-= 170
- 3 210
- 9 225
- 1120 229
- 259
- # c2p show -act 263
- 1,0 273
- 277
- 1,0 278
- 1+0 280
- 1210 292
- 12?0 294
- 120 296
- 120 298
- ++0 300
- +)0 301
- # ip show -mcast 316
- IP Multicast Routing Table 316
- 1+0 320
- 1)0 321
- 110 322
- 10 323
- 1?0 324
- 1*0 325
- 10 326
- 1,0 327
- 10 328
- 120 329
- +0 330
- $/0/$0/5 332
- (100715, rev. 1.x) 333
- (100715, rev. 2.x) 333
- (103346) 333
- (103798) 333
- 0 338
- 20 339
- ?0 343
- ??0 344
- ?*0 345
- ?0 346
- ?,0 347
- ?0 348
- ?20 349
- *+0 350
- *)0 351
- *10 352
- 356
- $/0/$0/5 359
- *0 365
- 0 366
- ,0 367
- 0 368
- ,0 387
- 0 388
- ( 392
- ( Ext - 0) 408
- )?0+201++ 410
- ?)+0 410
- ?),0 417
- ?10 423
- ?1?0 424
- ?1*0 425
- ?10 426
- ?1,0 427
- ?*0 458
- ?*20 459
- ?+0 460
- ?)0 461
- ??0 464
- ?*0 465
- ?,0 467
- & 3-= 476
- 477
- ! 477
- ( )! 477
- 3*$! 480
- $! <@ 480
- ))0+)01++ 481
- ?)0 481
- ??0 484
- ?,0 487
- ?20 489
- ?210 492
- ?2?0 494
- -*$! 497
- ?20 498
- &C -* 531
- & 2*-* 537
- Capacity 544
- MaxCapacity MaxGuardBand 544
- BfOD BfPerm 544
- 545
- 3 A 7 545
- * 3 545
- % 550
- ' $ 551
- -6)' -D 555
- **0 556
- **,0 557
- **0 558
- **20 559
- *+0 560
- *)0 561
- *10 562
- *0 563
- *?0 564
- **0 565
- *0 566
- *,0 567
- *0 568
- *20 569
- *,+0 570
- *,)0 571
- *,10 572
- *,0 573
- *,?0 574
- *,*0 575
- *,0 576
- *,,0 577
- *,0 578
- *,20 579
- *+0 580
- *)0 581
- *10 582
- *0 583
- *?0 584
- **0 585
- *0 586
- *,0 587
- *0 588
- *20 589
- *2+0 590
- *2)0 591
- *210 592
- *20 593
- *2?0 594
- *2*0 595
- *20 596
- *2,0 597
- *20 598
- *220 599
- ++0 600
- +)0 601
- +10 602
- +0 603
- +?0 604
- +*0 605
- +0 606
- )10 612
- )*0 615
- )0 616
- ),0 617
- )0 618
- )20 619
- 1+0 620
- 1)0 621
- 110 622
- 10 623
- 1*0 625
- 10 626
- 1,0 627
- 10 628
- 120 629
- +0 630
- )0 631
- 10 632
- 0 633
- ?0 634
- *0 635
- 0 636
- G <3=<3 637
- 3<<=' 3 638
© 2020, manymanuals.es. Todos los derechos reservados | 0.033 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales