Shiro ADSL 2/2+ Ethernet Modem Uživatelský manuál Strana 573
- Strana / 638
- Tabulka s obsahem
- KNIHY
Hodnocené. / 5. Na základě hodnocení zákazníků
)*+,,*
-./
!
))0+)01++,
=!
)(+
42!
*,0
STLF-NA-TRD-REQ-1860 The PEP solution adopted in SatLife system shall be compliant with SatLabs
PEP solution.
T NERA: by design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1870 The PEP solution adopted in SatLife system shall be applicable for Star and
Mesh scenarios
T NERA: by design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1880 The PEP solution shall be transparent to users on either end of the Satellite
Network. This means that a subscriber shall not be required to load any
software, nor to be required to change any settings to be able to use any and
all features of the PEP.
T NERA: : by design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1890 Functionally the PEP protocol stack shall look as follows: T NERA: by design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1900 TCP-PEP functionality shall:
Implement a TCP proxy towards the host and the server
Efficiently transmit TCP data over the satellite network
T NERA:by design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1910 The design should separate these two functions, so that the PEP protocol
can be replaced, modified or that several PEP clients can be embedded in
the RCS terminal without affecting the TCP proxy functionality and vice versa
T NERA: by design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1920 It shall be possible to accelerate TCP traffic between two RCSTs running
embedded PEP clients without the need of routing the TCP traffic towards a
TCP PEP server.
T NERA
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1930 TCP PEP client shall be compatible with a standard TCP PEP solution for a
transparent system. Meaning that is shall be possible to use the same TCP
PEP client embedded in the RCS terminal in Mesh and Transparent systems
T NERA
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1940 The TCP-PEP solution shall be transparent to:
IP source and destination addresses
Local and remote ports
TTL
QoS
T NERA
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1950 The TCP-PEP solution shall provide end-user transparency to end users
achieved by split-connection TCP-based PEP as outlined in RFC2488 and
RFC3135
T NERA: By design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1960 The TCP-PEP solution shall operate totally transparent to the end systems,
i.e. the end systems shall not need to know whether TCP PEP is being
employed or not.
T NERA: By design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
STLF-NA-TRD-REQ-1970 The TCP-PEP solution shall be symmetric i.e. the TCP PEP client shall use
the same TCP enhancement mechanisms for both the forward and return link
T NERA: By design
STLF_IF_RCST_PEPM
STLF_IO_INTER
STLF_IO_INTRA_MESH
- 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.cz. Všechna práva vyhrazena. | 0.035 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentáře k této Příručce