rfc5168.XML Schema for Media Control

合集下载

机顶盒与IPTV业务运营平台接口技术规范V2.2(EPG部分)

节目映射表
PSI Program Specific Information 节目专有信息
3
PDF 文件使用 "pdfFactory Pro" 试用版本创建
RPC Remote Procedure Call
远程过程调用
RTCP Real-time Transport Control Protocol 实时传输控
网络时间协议
OS
Operation System
操作系统
PAT Program Association Table 节目组合表
PCR Program Clock Reference
节目时钟参考
PES Packet elementary stream
打包的基本码流
PMT Program Map Table
国际标准化组织
MAC
Media Access Control
媒体访问控制层
MPEG2 Moving Picture Experts Group 2 活动图像专家组 2
MPTS Multiple Programs Transport Stream 多节目传输流
NTP Network Time Protocol
文件编号：SHDX/ZS/CZ/JG/002/A/2008
中国电信集团上海市电信公司机顶盒与 IPTV 业务运营平台接口技术规范 V2.2
1. 目的本规范是在中国电信集团公司发布的《机顶盒与 IPTV 业务运营
平台接口技术规范 V2.0》的基础上，根据中国电信上海公司 IPTV 运营的实际情况，进一步调整修订而成的。
是注日期的引用文件，其随后所有的修改单（不包括勘误的内容）或修订版均不适用于本标准，然而，鼓励根据本标准达成协议的各方研究是否可使用这些文件的最新版本。凡是不注日期的引用文件，其最新版本适用于本标准。

中移动家庭网关终端技术规范v3.0.0

中国移动通信企业标准家庭网关终端技术规范版本号：3.0.0中国移动通信集团公司发布╳╳╳╳-╳╳-╳╳发布 ╳╳╳╳-╳╳-╳╳实施QB-╳╳-╳╳╳-╳╳╳╳ T e c h n i c a l S p e c i f i c a t i o n f o r H o m e G a t e w a y目录3.术语、定义和缩略语 ....................................................................................... 错误!未指定书签。

USB扩展及管理（可选）................................................................................ 错误!未指定书签。

DLNA（可选）............................................................................................................... 错误!未指定书签。

5.6.硬件要求....................................................................................................... 错误!未指定书签。

设备面板标识要求........................................................................................... 错误!未指定书签。

操作管理 ...................................................................................................................... 错误!未指定书签。

直连sap rfc 参数结构

直连sap rfc 参数结构（原创版）目录1.直连 SAP RFC 的概念与原理2.直连 SAP RFC 的参数结构3.直连 SAP RFC 接口调用的步骤4.直连 SAP RFC 的注意事项正文一、直连 SAP RFC 的概念与原理直连 SAP RFC（Remote Function Call）是指通过 SAP 提供的远程函数调用接口，实现对 SAP 系统的直接操作。

这种方式可以有效减少系统间的耦合度，提高系统的可维护性和扩展性。

通过使用 SAP RFC 接口，可以在非 SAP 系统中实现对 SAP 系统的数据查询、修改、删除等操作。

二、直连 SAP RFC 的参数结构直连 SAP RFC 的参数结构主要包括以下几个部分：1.接口名称：用于区分不同的 RFC 接口，通常为接口的唯一标识符。

2.接口版本：接口的版本号，用于表示接口的实现方式和功能特性。

3.接口操作：接口支持的操作类型，例如数据查询、数据修改等。

4.参数列表：包含接口调用所需的参数，通常包括输入参数和输出参数。

参数需要按照一定的顺序排列，并且需要与接口定义中的参数顺序一致。

三、直连 SAP RFC 接口调用的步骤1.新建一个文件夹存放 WSDL 文件，将 SAP 提供的 WSDL 文件存储到其中。

2.选中需要调用的 WSDL 文件，右键选择“新建 - 其他-Web 服务 - 客户端”，创建接口代码。

3.将流程调用接口存放在 Weaver.interfaces.workflow.action 下，具体路径自行确认。

4.编写调用接口的代码，并实现参数的传递和结果的处理。

四、直连 SAP RFC 的注意事项1.在使用直连 SAP RFC 接口时，需要确保 SAP 系统的可用性和稳定性。

2.接口调用需要遵循 SAP RFC 的规范，例如参数的顺序、数据类型的映射等。

3.在编写调用接口的代码时，需要处理好异常情况，确保程序的健壮性。

机顶盒与IPTV业务运营平台接口技术规范V2.2(EPG部分)

STB
EPG 服务系统
a）HTTP GET 请求
b）HTTP 响应
6.1.2.
图 7-1-1-1 机顶盒访问 EPG 首页流程图
EPG 首页请求
承载协议：HTTP GET
接口方向：机顶盒–〉EPG 服务系统
接口地址：http://EPGDomain
接口功能：机顶盒向 EPG 服务系统请求 EPG 首页
可扩展标记语言 XML 数据定义文件
5. 机顶盒与 IPTV 业务运营平台接口框架 5.1.机顶盒与 IPTV 业务运营平台接口描述图
机顶盒与 IPTV 业务运营平台有以下逻辑接口： a).与业务管理平台的接口（S1） b).与 EPG 服务系统的接口（S2） c).与增值业务平台的接口（S3） d).与 TS 内容分发系统的接口（S4-T） e).与 ISMA 内容分发系统的接口（S4-I） f).与 DRM 系统的接口（C4） g).与通信服务系统的接口（S5） h).与终端管理系统的接口（S6）所有接口在系统中的位置，如图 5-1-1 所示：
机顶盒的 MAC 地址，格 String
17
式为：xx:xx:xx:xx:xx:xx
O M M
O
http://EPGDomain?UserID=1234567&UserGroupNMB=us010018&E
PGGroupNMB=sh001018&STBID=011010000021E030002100300004C7E7&
7
PDF 文件使用 "pdfFactory Pro" 试用版本创建
机顶盒通过 S6 接口与终端管理系统交互，完成终端管理、软件升级、性能监测等功能

5616 网络风暴抑制

MA5616的报文抑制功能默认为7，抑制比最小390kbps，最大为9265kbps，包转发率为763pps。

为了解决近期的用户异常错误678/651的问题，主要是由于上行大流量的未知报文导致下行拥塞导致。

建议在MA5616的上行端口配置报文抑制，抑制模板为2，以下是配置脚本，请参考：做完以下步骤,board reset 0/1TZ-XICANGQIAOKOU-KD-MA5616-01(config)#interface eth 0/0TZ-XICANGQIAOKOU-KD-MA5616-01(config-if-eth-0/0)#display traffic-suppress all Traffic suppression ID definition:---------------------------------------------------------------------NO. Min bandwidth(kbps) Max bandwidth(kbps) Package number(pps)---------------------------------------------------------------------1 6 145 122 12 291 243 24 582 484 48 1153 955 97 2319 1916 195 4639 3827 390 9265 7638 781 18531 15269 1562 37063 305210 3125 74126 610411 6249 148241 1220712 12499 296483 2441413 0 0 0------------------------------------------------------------------------------------------------------------------------------------------PortID Broadcast_index Multicast_index Unicast_index---------------------------------------------------------------------0 7 7 71 7 7 7---------------------------------------------------------------------TZ-XICANGQIAOKOU-KD-MA5616-01(config-if-eth-0/0)#traffic-suppress all multicast value 2TZ-XICANGQIAOKOU-KD-MA5616-01(config-if-eth-0/0)#traffic-suppress all broadcast value 2TZ-XICANGQIAOKOU-KD-MA5616-01(config-if-eth-0/0)#traffic-suppress all unicast value 2 TZ-XICANGQIAOKOU-KD-MA5616-01#display board 0/0---------------------------------------Board Name : H831CCUBBoard Status : Active normal---------------------------------------Subboard[0]: H831EP1A Status: Normal------------------------------------------------------------------------------Port Port COMBO Optic MDI Speed Duplex Flow- Active LinkType Mode Status (Mbps) Ctrl State------------------------------------------------------------------------------0 GE electric - auto auto auto off active offline------------------------------------------------------------------------------Note: For a 1000 M, electrical port in the full-duplex mode, setting MDI toany value is invalid-----------------------------------------------------------------------------Port Port Type MAC Regist State Link State-----------------------------------------------------------------------------1 EPON 0025-9EDA-92B9 EXT-OAM-registered UP-----------------------------------------------------------------------------TZ-XICANGQIAOKOU-KD-MA5616-01(config-if-eth-0/0)#display traffic-suppress all Traffic suppression ID definition:---------------------------------------------------------------------NO. Min bandwidth(kbps) Max bandwidth(kbps) Package number(pps)---------------------------------------------------------------------1 6 145 122 12 291 243 24 582 484 48 1153 955 97 2319 1916 195 4639 3827 390 9265 7638 781 18531 15269 1562 37063 305210 3125 74126 610411 6249 148241 1220712 12499 296483 2441413 0 0 0------------------------------------------------------------------------------------------------------------------------------------------PortID Broadcast_index Multicast_index Unicast_index---------------------------------------------------------------------0 2 2 21 2 2 2---------------------------------------------------------------------。

{业务管理}网络短消息业务技术要求精编

{业务管理}网络短消息业务技术要求Q/CT 2088-2010 中国电信集团公司发布目录目录I前言III短消息业务技术要求11范围12引用标准13缩略语14业务定义25业务特征25.1短消息的应用类别25.2短消息回执25.3短消息的有效期25.4短消息的重发35.5短消息的长度35.6短消息的编码格式35.7短消息的优先级35.8短消息的定时发送35.9短消息的群发35.10缓存短消息下发36业务编号47系统架构47.1模块说明47.2接口说明48信令流程58.1IMS用户注册/第三方注册/缓存短消息下发5 8.2IMS用户－IMS用户68.2.1短消息提交68.2.2短消息下发88.2.3发送方SMC递送到接收方SMC98.2.4超长短消息138.2.5SMC发送短消息失败－遇到临时性错误14 8.2.6SMC发送短消息失败－遇到永久性错误15 8.2.7SMC发送回执失败－遇到临时性错误15 8.2.8SMC发送回执失败－遇到永久性错误16 8.3IMS用户－其他网络用户178.3.1短消息提交178.3.2超长短消息提交198.4其他网络用户－IMS用户218.4.1短消息下发218.4.2超长短消息下发229业务实现239.1iFC设置239.2组网方式2310设备要求2410.1HSS2410.2S-CSCF2410.3短消息中心2410.4ENUM/DNS2510.5I-CSCF2510.6终端25附录ASIP协议针对消息处理的XML扩展26A.1短消息操作类型26A.2SMML操作结构26A.3SMML操作参数27A.3.1<shortmessage>成员参数27A.3.2<receipt>成员参数29A.4XMLSchema32A.5SMML实例36附录BSIP与SMPP协议的映射38B.1参数映射38B.2失败原因映射39B.2.1SMPP响应到SIP短消息发送失败原因的映射39B.2.2SIP响应码到SMPP短消息发送失败原因的映射40B.2.3SMPP短消息发送失败原因与SIP短消息发送失败原因的映射41前言本标准主要依据《中国电信SIP短消息中心设备总体技术要求》（V1.0版）、《中国电信SIP短消息中心SIPSMML接口技术规范》（V1.0版）和3GPP2X.S0048-0“ShortMessageServiceOverIMSv1.0”的相关内容，结合中国电信IMS 试点的相关成果和经验进行编写，随着技术和业务的发展，还将制定后续的相关标准。

[生活]计算机专业英语词汇缩写大全

[生活]计算机专业英语词汇缩写大全计算机专业英语词汇缩写大全计算机专业英语词汇缩写大全(J-Z)2010年01月06日星期三 12:47J J2EE — Java 2 Enterprise Edition J2ME — Java 2 Micro Edition J2SE — Java 2 Standard Edition JAXB — Java Architecture for XML Binding JAX-RPC — Java XML for Remote Procedure Calls JAXP — Java API for XML Processing JBOD — Just a Bunch of Disks JCE — Java Cryptography Extension JCL — Job Control Language JCP — Java Community Process JDBC — Java Database Connectivity JDK — Java Development KitJES — Job Entry SubsystemJDS — Java Desktop SystemJFC — Java Foundation Classes JFET — Junction Field-Effect Transistor JFS — IBM Journaling File System JINI — Jini Is Not InitialsJIT — Just-In-TimeJMX — Java Management Extensions JMS — Java Message Service JNDI — Java Naming and Directory Interface JNI — Java Native InterfaceJPEG — Joint Photographic Experts Group JRE — Java Runtime Environment JS — JavaScriptJSON — JavaScript Object NotationJSP — Jackson Structured Programming JSP — JavaServer PagesJTAG — Joint Test Action Group JUG — Java Users Group JVM — Java Virtual Machine jwz — Jamie ZawinskiKK&R — Kernighan and Ritchie KB — KeyboardKb — KilobitKB — KilobyteKB — Knowledge BaseKDE — K Desktop Environment kHz — KilohertzKISS — Keep It Simple, Stupid KVM — Keyboard, Video, Mouse LL10N — LocalizationL2TP — Layer 2 Tunneling Protocol LAMP — Linux Apache MySQL Perl LAMP — Linux Apache MySQL PHP LAMP — Linux Apache MySQL Python LAN —Local Area Network LBA — Logical Block Addressing LCD — Liquid Crystal Display LCOS — Liquid Crystal On Silicon LDAP — Lightweight Directory Access ProtocolLE — Logical ExtentsLED — Light-Emitting Diode LF — Line FeedLF — Low FrequencyLFS — Linux From Scratch lib — libraryLIF — Low Insertion Force LIFO — Last In First Out LILO — Linux LoaderLKML — Linux Kernel Mailing List LM — Lan ManagerLGPL — Lesser General Public License LOC — Lines of CodeLPI — Linux Professional Institute LPT — Line Print Terminal LSB — Least Significant Bit LSB — Linux Standard Base LSI — Large-Scale IntegrationLTL — Linear Temporal Logic LTR — Left-to-RightLUG — Linux User Group LUN — Logical Unit Number LV — Logical VolumeLVD — Low Voltage Differential LVM — Logical Volume Management LZW — Lempel-Ziv-Welch MMAC — Mandatory Access Control MAC — Media Access Control MAN —Metropolitan Area Network MANET — Mobile Ad-Hoc Network MAPI —Messaging Application Programming InterfaceMb — MegabitMB — MegabyteMBCS — Multi Byte Character Set MBR — Master Boot RecordMCA — Micro Channel Architecture MCSA — Microsoft Certified Systems AdministratorMCSD — Microsoft Certified Solution DeveloperMCSE — Microsoft Certified Systems Engineer MDA — Mail Delivery AgentMDA — Model-Driven Architecture MDA — Monochrome Display Adapter MDF — Main Distribution FrameMDI — Multiple Document Interface ME — [Windows] Millennium Edition MF — Medium FrequencyMFC — Microsoft Foundation Classes MFM — Modified Frequency Modulation MGCP — Media Gateway Control Protocol MHz — Megahertz MIB — Management Information Base MICR — Magnetic Ink Character Recognition MIDI — Musical Instrument Digital Interface MIMD —Multiple Instruction, Multiple Data MIMO — Multiple-Input Multiple-Output MIPS — Million Instructions Per Second MIPS — Microprocessor without Interlocked Pipeline StagesMIS — Management Information Systems MISD — Multiple Instruction, Single Data MIT — Massachusetts Institute of Technology MIME —Multipurpose Internet Mail ExtensionsMMDS — Mortality Medical Data System MMI — Man Machine Interface. MMIO — Memory-Mapped I/OMMORPG — Massively Multiplayer Online Role-Playing GameMMU — Memory Management Unit MMX — Multi-Media Extensions MNG —Multiple-image Network Graphics MoBo — MotherboardMOM — Message-Oriented Middleware MOO — MUD Object OrientedMOSFET — Metal-Oxide Semiconductor FET MOTD — Message Of The Day MPAA — Motion Picture Association of America MPEG — Motion Pictures Experts Group MPL — Mozilla Public License MPLS —Multiprotocol Label Switching MPU — Microprocessor Unit MS — Memory StickMS — MicrosoftMSB — Most Significant Bit MS-DOS — Microsoft DOSMT — Machine TranslationMTA — Mail Transfer AgentMTU — Maximum Transmission Unit MSA — Mail Submission Agent MSDN — Microsoft Developer Network MSI — Medium-Scale Integration MSI — Microsoft InstallerMUA — Mail User AgentMUD — Multi-User DungeonMVC — Model-View-ControllerMVP — Most Valuable Professional MVS — Multiple Virtual Storage MX — Mail exchangeMXF — Material Exchange Format NNACK — Negative ACKnowledgement NAK — Negative AcKnowledge Character NAS — Network-Attached Storage NAT — Network Address Translation NCP — NetWare Core ProtocolNCQ — Native Command Queuing NCSA — National Center for Supercomputing ApplicationsNDPS — Novell Distributed Print Services NDS — Novell Directory Services NEP — Network Equipment Provider NEXT — Near-End CrossTalk NFA — Nondeterministic Finite Automaton GNSCB — Next-Generation Secure Computing BaseNFS — Network File SystemNI — National InstrumentsNIC — Network Interface Controller NIM — No Internal Message NIO — New I/ONIST — National Institute of Standards and TechnologyNLP — Natural Language Processing NLS — Native Language Support NP — Non-Deterministic Polynomial-TimeNPL — Netscape Public License NPU — Network Processing Unit NS —NetscapeNSA — National Security Agency NSPR — Netscape Portable Runtime NMI — Non-Maskable Interrupt NNTP — Network News Transfer Protocol NOC — Network Operations Center NOP — No OPerationNOS — Network Operating System NPTL — Native POSIX Thread Library NSS — Novell Storage Service NSS — Network Security Services NSS —Name Service SwitchNT — New TechnologyNTFS — NT FilesystemNTLM — NT Lan ManagerNTP — Network Time Protocol NUMA — Non-Uniform Memory Access NURBS — Non-Uniform Rational B-Spline NVR - Network Video Recorder NVRAM — Non-Volatile Random Access Memory OOASIS — Organization for the Advancement of StructuredInformation StandardsOAT — Operational Acceptance Testing OBSAI — Open Base Station Architecture InitiativeODBC — Open Database Connectivity OEM — Original Equipment Manufacturer OES — Open Enterprise ServerOFTC — Open and Free Technology Community OLAP — Online Analytical Processing OLE — Object Linking and Embedding OLED — Organic LightEmitting Diode OLPC — One Laptop per Child OLTP — Online Transaction Processing OMG — Object Management Group OO — Object-Oriented OO — Open OfficeOOM — Out of memoryOOo — OOP — Object-Oriented Programming OPML — Outline Processor Markup Language ORB — Object Request Broker ORM — Oject-Relational Mapping OS — Open SourceOS — Operating SystemOSCON — O'Reilly Open Source Convention OSDN — Open Source Developer Network OSI — Open Source Initiative OSI — Open Systems Interconnection OSPF — Open Shortest Path First OSS — Open Sound SystemOSS — Open-Source SoftwareOSS — Operations Support System OSTG — Open Source Technology Group OUI — Organizationally Unique Identifier PP2P — Peer-To-PeerPAN — Personal Area Network PAP — Password Authentication Protocol PARC — Palo Alto Research Center PATA — Parallel ATAPC — Personal ComputerPCB — Printed Circuit BoardPCB — Process Control BlockPCI — Peripheral Component Interconnect PCIe — PCI ExpressPCL — Printer Command Language PCMCIA — Personal Computer Memory Card InternationalAssociationPCM — Pulse-Code ModulationPCRE — Perl Compatible Regular Expressions PD — Public Domain PDA — Personal Digital Assistant PDF — Portable Document Format PDP — Programmed Data Processor PE — Physical ExtentsPEBKAC — Problem Exists Between Keyboard And ChairPERL — Practical Extraction and Reporting LanguagePGA — Pin Grid ArrayPGO — Profile-Guided Optimization PGP — Pretty Good PrivacyPHP — PHP: Hypertext Preprocessor PIC — Peripheral Interface Controller PIC — Programmable Interrupt Controller PID — Proportional-Integral-Derivative PID — Process IDPIM — Personal Information Manager PINE — Program for Internet News & EmailPIO — Programmed Input/Output PKCS — Public Key Cryptography Standards PKI — Public Key Infrastructure PLC — Power Line Communication PLC — Programmable Logic Controller PLD — Programmable Logic Device PL/I — Programming Language One PL/M — Programming Language for MicrocomputersPL/P — Programming Language for Prime PLT — Power Line Telecoms PMM — POST Memory ManagerPNG — Portable Network Graphics PnP — Plug-and-PlayPoE — Power over EthernetPOP — Point of PresencePOP3 — Post Office Protocol v3 POSIX — Portable Operating System Interface POST — Power-On Self TestPPC — PowerPCPPI — Pixels Per InchPPP — Point-to-Point Protocol PPPoA — PPP over ATMPPPoE — PPP over EthernetPPTP — Point-to-Point Tunneling Protocol PS — PostScriptPS/2 — Personal System/2PSU — Power Supply UnitPSVI — Post-Schema-Validation Infoset PV — Physical VolumePVG — Physical Volume GroupPVR — Personal Video RecorderPXE — Preboot Execution Environment PXI — PCI eXtensions for Instrumentation QQDR — Quad Data RateQA — Quality AssuranceQFP — Quad Flat PackageQoS — Quality of ServiceQOTD — Quote of the DayQt — Quasar ToolkitQTAM — Queued Teleprocessing Access Method RRACF — Resource Access Control Facility RAD — Rapid Application Development RADIUS — Remote Authentication Dial In User Service RAID — Redundant Array of Independent Disks RAID — Redundant Array of Inexpensive Disks RAIT — Redundant Array of Inexpensive Tapes RAM —Random Access MemoryRARP — Reverse Address Resolution Protocol RAS — Remote Access ServiceRC — Region CodeRC — Release CandidateRC — Run CommandsRCS — Revision Control SystemRDBMS — Relational Database Management SystemRDF — Resource Description Framework RDM — Relational Data Model RDS — Remote Data ServicesREFAL — REcursive Functions Algorithmic LanguageREST — Representational State Transfer regex — Regular Expression regexp — Regular Expression RF — Radio FrequencyRFC — Request For CommentsRFI — Radio Frequency Interference RFID — Radio Frequency Identification RGB — Red, Green, BlueRGBA — Red, Green, Blue, Alpha RHL — Red Hat LinuxRHEL — Red Hat Enterprise Linux RIA — Rich Internet Application RIAA — Recording Industry Association of AmericaRIP — Raster Image Processor RIP — Routing Information Protocol RISC — Reduced Instruction Set Computer RLE — Run-Length Encoding RLL — Run-Length LimitedRMI — Remote Method Invocation RMS — Richard Matthew Stallman ROM — Read Only MemoryROMB — Read-Out Motherboard RPC — Remote Procedure Call RPG —Report Program Generator RPM — RPM Package ManagerRSA — Rivest Shamir Adleman RSI — Repetitive Strain Injury RSS —Rich Site Summary, RDF Site Summary, or Really SimpleSyndicationRTC — Real-Time ClockRTE — Real-Time EnterpriseRTL — Right-to-LeftRTOS — Real Time Operating System RTP — Real-time Transport Protocol RTS — Ready To SendRTSP — Real Time Streaming Protocol SSaaS — Software as a Service SAN — Storage Area NetworkSAR — Search And Replace[1]SATA — Serial ATASAX — Simple API for XMLSBOD — Spinning Beachball of Death SBP-2 — Serial Bus Protocol 2 sbin — superuser binarySBU — Standard Build UnitSCADA — Supervisory Control And Data AcquisitionSCID — Source Code in Database SCM — Software Configuration Management SCM — Source Code Management SCP — Secure Copy SCPI — Standard Commands for Programmable Instrumentation SCSI — Small Computer System Interface SCTP — Stream Control Transmission Protocol SD — Secure DigitalSDDL — Security Descriptor Definition LanguageSDI — Single Document InterfaceSDIO — Secure Digital Input OutputSDK — Software Development KitSDL — Simple DirectMedia LayerSDN — Service Delivery NetworkSDP — Session Description ProtocolSDR — Software-Defined RadioSDRAM — Synchronous Dynamic Random Access MemorySDSL — Symmetric DSLSE — Single EndedSEAL — Semantics-directed Environment Adaptation Language SEI — Software Engineering InstituteSEO — Search Engine OptimizationSFTP — Secure FTPSFTP — Simple File Transfer ProtocolSFTP — SSH File Transfer ProtocolSGI — Silicon Graphics, IncorporatedSGML — Standard Generalized Markup LanguageSHA — Secure Hash AlgorithmSHDSL — Single-pair High-speed Digital Subscriber LineSIGCAT — Special Interest Group on CD-ROM Applications andTechnologySIGGRAPH — Special Interest Group on GraphicsSIMD — Single Instruction, Multiple DataSIMM — Single Inline Memory ModuleSIP — Session Initiation ProtocolSIP — Supplementary Ideographic PlaneSISD — Single Instruction, Single Data SLED — SUSE LinuxEnterprise Desktop SLES — SUSE Linux Enterprise Server SLI — Scalable Link Interface SLIP — Serial Line Internet Protocol SLM — Service Level Management SLOC — Source Lines of Code SPMD — Single Program, Multiple Data SMA — SubMiniature version A SMB — Server Message Block SMBIOS — System Management BIOS SMIL — Synchronized Multimedia Integration LanguageS/MIME — Secure/Multipurpose Internet Mail ExtensionsSMP — Supplementary Multilingual Plane SMP — Symmetric Multi-Processing SMS — Short Message Service SMS — System Management Server SMT — Simultaneous Multithreading SMTP — Simple Mail Transfer Protocol SNA — Systems Network Architecture SNMP — Simple Network Management Protocol SOA — Service-Oriented Architecture SOE — Standard Operating Environment SOAP — Simple Object Access Protocol SoC — System-on-a-ChipSO-DIMM — Small Outline DIMM SOHO — Small Office/Home OfficeSOI — Silicon On InsulatorSP — Service PackSPA — Single Page Application SPF — Sender Policy Framework SPI —Serial Peripheral Interface SPI — Stateful Packet Inspection SPARC —Scalable Processor Architecture SQL — Structured Query Language SRAM —Static Random Access Memory SSD — Software Specification Document SSD - Solid-State DriveSSE — Streaming SIMD Extensions SSH — Secure ShellSSI — Server Side Includes SSI — Single-System Image SSI — Small-Scale Integration SSID — Service Set Identifier SSL — Secure Socket Layer SSP — Supplementary Special-purpose Plane SSSE — Supplementary Streaming SIMD Extensionssu — superuserSUS — Single UNIX Specification SUSE — Software und System-Entwicklung SVC — Scalable Video Coding SVG — Scalable Vector Graphics SVGA — Super Video Graphics Array SVD — Structured VLSI Design SWF —Shock Wave FlashSWT — Standard Widget Toolkit Sysop — System operatorTTAO — Track-At-OnceTB — TerabyteTcl — Tool Command Language TCP — Transmission Control Protocol TCP/IP — Transmission Control Protocol/Internet ProtocolTCU — Telecommunication Control Unit TDMA — Time Division Multiple Access TFT — Thin Film Transistor TI — Texas Instruments TLA — Three-Letter Acronym TLD — Top-Level DomainTLS — Thread-Local Storage TLS — Transport Layer Security tmp —temporaryTNC — Terminal Node Controller TNC — Threaded Neill-Concelman connector TSO — Time Sharing OptionTSP — Traveling Salesman Problem TSR — Terminate and Stay Resident TTA — True Tap AudioTTF — TrueType FontTTL — Transistor-Transistor Logic TTL — Time To LiveTTS — Text-to-SpeechTTY — TeletypeTUCOWS — The Ultimate Collection of Winsock SoftwareTUG — TeX Users GroupTWAIN - Technology Without An Interesting NameUUAAG — User Agent Accessibility Guidelines UAC — User Account Control UART — Universal Asynchronous Receiver/Transmitter UAT — User Acceptance Testing UCS — Universal Character SetUDDI — Universal Description, Discovery, and Integration UDMA — Ultra DMAUDP — User Datagram Protocol UE — User ExperienceUEFI — Unified Extensible Firmware Interface UHF — Ultra High Frequency UI — User InterfaceUL — UploadULA — Uncommitted Logic Array UMA — Upper Memory AreaUMB — Upper Memory BlockUML — Unified Modeling Language UML — User-Mode LinuxUMPC — Ultra-Mobile Personal Computer UNC — Universal Naming Convention UPS — Uninterruptible Power Supply URI — Uniform Resource Identifier URL — Uniform Resource Locator URN — Uniform Resource Name USB — Universal Serial Bus usr — userUSR — U.S. RoboticsUTC — Coordinated Universal Time UTF — Unicode Transformation FormatUTP — Unshielded Twisted Pair UUCP — Unix to Unix CopyUUID — Universally Unique Identifier UVC — Universal Virtual Computer Vvar — variableVAX — Virtual Address eXtension VCPI — Virtual Control Program Interface VR — Virtual RealityVRML — Virtual Reality Modeling Language VB — Visual BasicVBA — Visual Basic for Applications VBS — Visual Basic Script VDSL — Very High Bitrate Digital Subscriber LineVESA — Video Electronics Standards AssociationVFAT — Virtual FATVFS — Virtual File SystemVG — Volume GroupVGA — Video Graphics ArrayVHF — Very High FrequencyVLAN — Virtual Local Area Network VLSM — Variable Length Subnet Mask VLB — Vesa Local BusVLF — Very Low FrequencyVLIW - Very Long Instruction Word— uinvac VLSI — Very-Large-Scale Integration VM — Virtual MachineVM — Virtual MemoryVOD — Video On DemandVoIP — Voice over Internet Protocol VPN — Virtual Private Network VPU — Visual Processing Unit VSAM — Virtual Storage Access Method VSAT — Very Small Aperture Terminal VT — Video Terminal?VTAM — Virtual Telecommunications Access MethodWW3C — World Wide Web Consortium WAFS — Wide Area File ServicesWAI — Web Accessibility Initiative WAIS — Wide Area Information Server WAN — Wide Area NetworkWAP — Wireless Access Point WAP — Wireless Application Protocol WAV — WAVEform audio format WBEM — Web-Based Enterprise Management WCAG — Web Content Accessibility Guidelines WCF — Windows Communication Foundation WDM — Wavelength-Division Multiplexing WebDAV — WWW Distributed Authoring and VersioningWEP — Wired Equivalent Privacy Wi-Fi — Wireless FidelityWiMAX — Worldwide Interoperability for Microwave AccessWinFS — Windows Future Storage WINS- Windows Internet Name Service WLAN — Wireless Local Area Network WMA — Windows Media Audio WMV — Windows Media VideoWOL — Wake-on-LANWOM — Wake-on-ModemWOR — Wake-on-RingWPA — Wi-Fi Protected Access WPAN — Wireless Personal Area Network WPF — Windows Presentation Foundation WSDL — Web Services Description Language WSFL — Web Services Flow Language WUSB — Wireless Universal Serial Bus WWAN — Wireless Wide Area Network WWID — World Wide Identifier WWN — World Wide NameWWW — World Wide WebWYSIWYG — What You See Is What You Get WZC — Wireless Zero Configuration WFI — Wait For InterruptXXAG — XML Accessibility Guidelines XAML — eXtensible Application Markup LanguageXDM — X Window Display Manager XDMCP — X Display Manager Control Protocol XCBL — XML Common Business Library XHTML — eXtensible Hypertext Markup Language XILP — X Interactive ListProc XML —eXtensible Markup Language XMMS — X Multimedia SystemXMPP — eXtensible Messaging and Presence ProtocolXMS — Extended Memory SpecificationXNS — Xerox Network Systems XP — Cross-PlatformXP — Extreme ProgrammingXPCOM — Cross Platform Component Object ModelXPI — XPInstallXPIDL — Cross-Platform IDLXSD — XML Schema Definition XSL — eXtensible Stylesheet Language XSL-FO — eXtensible Stylesheet Language Formatting Objects XSLT — eXtensible Stylesheet Language TransformationsXSS — Cross-Site ScriptingXTF — eXtensible Tag Framework XTF — eXtended Triton Format XUL —XML User Interface Language YY2K — Year Two ThousandYACC — Yet Another Compiler Compiler YAML — YAML Ain't Markup Language YAST — Yet Another Setup Tool ZZCAV — Zone Constant Angular Velocity ZCS — Zero Code Suppression ZIF — Zero Insertion ForceZIFS — Zero Insertion Force Socket ZISC — Zero Instruction Set Computer ZOPE — Z Object Publishing Environment ZMA — Zone Multicast Address。

rfc相关设置及使用

rfc相关设置及使用RFC（Request for Comments）是一种用于定义互联网协议、标准和相关问题的文档。

RFC的格式由互联网工程任务组（IETF）统一规定，它们记录了网络技术的发展和演进过程。

在本文中，我们将介绍RFC相关的设置和使用。

1. 了解RFC的作用和历史：RFC是由IETF组织制定的一种标准化文档，它记录了互联网协议的设计、开发和演化过程。

RFC起源于20世纪60年代的ARPANET，是一种社区驱动的文档，通过共享和讨论来推动互联网技术的发展。

RFC文档旨在提供指南、建议和最佳实践，帮助网络技术人员解决问题。

2. 寻找和阅读RFC文档：RFC文档可以在互联网上免费获取，IETF的官方网站和其他资源库都有存档。

这些文档按照顺序编号，并且以RFC开头，比如RFC 791定义了IPv4协议。

通过搜索引擎或在IETF网站上使用关键词搜索，可以找到特定主题的RFC文档。

阅读RFC文档时，应该注意文档的状态，有一些可能已经被更新或废弃。

3. 使用RFC文档：RFC文档在网络技术的发展过程中起着重要的指导作用。

它们提供了协议规范、算法实现、安全性和隐私等方面的建议。

网络管理员、网络工程师和开发人员可以使用RFC文档来了解和理解特定协议或标准的设计原理和要求。

此外，RFC文档还常用于进行互联网协议的实现、编程和配置。

4. 参与RFC的制定过程：RFC并不是静止的文件，而是一个持续演进的过程。

任何人都可以参与到RFC的制定过程中。

要参与RFC的制定，可以加入IETF并参与相关的工作组或邮件列表。

通过这种方式，个人可以提出改进建议，参与讨论和标准化的制定。

5. 遵循RFC的指导原则：在网络技术领域，遵循RFC的指导原则是至关重要的。

这些指导原则包括设计原则、协议分层、安全性和互操作性等要求。

遵循RFC的指导原则可以确保网络协议的正确性、稳定性和可靠性，同时也可以促进网络技术的发展和创新。

总结起来，RFC在互联网技术领域起着重要的作用，它们记录了互联网协议的发展历程和指导原则。

rfc5881.Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)

Internet Engineering Task Force (IETF) D. Katz Request for Comments: 5881 D. Ward Category: Standards Track Juniper Networks ISSN: 2070-1721 June 2010 Bidirectional Forwarding Detection (BFD)for IPv4 and IPv6 (Single Hop)AbstractThis document describes the use of the Bidirectional ForwardingDetection (BFD) protocol over IPv4 and IPv6 for single IP hops.Status of This MemoThis is an Internet Standards Track document.This document is a product of the Internet Engineering Task Force(IETF). It represents the consensus of the IETF community. It hasreceived public review and has been approved for publication by theInternet Engineering Steering Group (IESG). Further information onInternet Standards is available in Section 2 of RFC 5741.Information about the current status of this document, any errata,and how to provide feedback on it may be obtained at/info/rfc5881.Copyright NoticeCopyright (c) 2010 IETF Trust and the persons identified as thedocument authors. All rights reserved.This document is subject to BCP 78 and the IETF Trust’s LegalProvisions Relating to IETF Documents(/license-info) in effect on the date ofpublication of this document. Please review these documentscarefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e ofthe Trust Legal Provisions and are provided without warranty asdescribed in the Simplified BSD License.Katz & Ward Standards Track [Page 1]1. IntroductionOne very desirable application for Bidirectional Forwarding Detection (BFD) [BFD] is to track IPv4 and IPv6 connectivity between directlyconnected systems. This could be used to supplement the detectionmechanisms in routing protocols or to monitor router-hostconnectivity, among other applications.This document describes the particulars necessary to use BFD in this environment. Interactions between BFD and other protocols and system functions are described in the BFD Generic Applications document[BFD-GENERIC].1.1. Conventions Used in This DocumentThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [KEYWORDS]. 2. Applications and LimitationsThis application of BFD can be used by any pair of systemscommunicating via IPv4 and/or IPv6 across a single IP hop that isassociated with an incoming interface. This includes, but is notlimited to, physical media, virtual circuits, and tunnels.Each BFD session between a pair of systems MUST traverse a separatenetwork-layer path in both directions. This is necessary fordemultiplexing to work properly, and also because (by definition)multiple sessions would otherwise be protecting the same path.If BFD is to be used in conjunction with both IPv4 and IPv6 on aparticular path, a separate BFD session MUST be established for each protocol (and thus encapsulated by that protocol) over that link.If the BFD Echo function is used, transmitted packets are immediately routed back towards the sender on the interface over which they were sent. This may interact with other mechanisms that are used on thetwo systems that employ BFD. In particular, ingress filtering[BCP38] is incompatible with the way Echo packets need to be sent.Implementations that support the Echo function MUST ensure thatingress filtering is not used on an interface that employs the Echofunction or make an exception for ingress filtering Echo packets.An implementation of the Echo function also requires ApplicationProgramming Interfaces (APIs) that may not exist on all systems. Asystem implementing the Echo function MUST be capable of sendingKatz & Ward Standards Track [Page 2]packets to its own address, which will typically require bypassingthe normal forwarding lookup. This typically requires access to APIs that bypass IP-layer functionality.Please note that BFD is intended as an Operations, Administration,and Maintenance (OAM) mechanism for connectivity check and connection verification. It is applicable for network-based services (e.g.router-to-router, subscriber-to-gateway, LSP/circuit endpoints, andservice appliance failure detection). In these scenarios it isrequired that the operator correctly provision the rates at which BFD is transmitted to avoid congestion (e.g link, I/O, CPU) and falsefailure detection. It is not applicable for application-to-application failure detection across the Internet because it does not have sufficient capability to do necessary congestion detection andavoidance and therefore cannot prevent congestion collapse. Host-to- host or application-to-application deployment across the Internetwill require the encapsulation of BFD within a transport thatprovides "TCP-friendly" [TFRC] behavior.3. Initialization and DemultiplexingIn this application, there will be only a single BFD session between two systems over a given interface (logical or physical) for aparticular protocol. The BFD session must be bound to thisinterface. As such, both sides of a session MUST take the "Active"role (sending initial BFD Control packets with a zero value of YourDiscriminator), and any BFD packet from the remote machine with azero value of Your Discriminator MUST be associated with the session bound to the remote system, interface, and protocol.4. EncapsulationBFD Control packets MUST be transmitted in UDP packets withdestination port 3784, within an IPv4 or IPv6 packet. The sourceport MUST be in the range 49152 through 65535. The same UDP sourceport number MUST be used for all BFD Control packets associated with a particular session. The source port number SHOULD be unique among all BFD sessions on the system. If more than 16384 BFD sessions are simultaneously active, UDP source port numbers MAY be reused onmultiple sessions, but the number of distinct uses of the same UDPsource port number SHOULD be minimized. An implementation MAY usethe UDP port source number to aid in demultiplexing incoming BFDControl packets, but ultimately the mechanisms in [BFD] MUST be used to demultiplex incoming packets to the proper session.BFD Echo packets MUST be transmitted in UDP packets with destination UDP port 3785 in an IPv4 or IPv6 packet. The setting of the UDPsource port is outside the scope of this specification. TheKatz & Ward Standards Track [Page 3]destination address MUST be chosen in such a way as to cause theremote system to forward the packet back to the local system. Thesource address MUST be chosen in such a way as to preclude the remote system from generating ICMP or Neighbor Discovery Redirect messages. In particular, the source address SHOULD NOT be part of the subnetbound to the interface over which the BFD Echo packet is beingtransmitted, and it SHOULD NOT be an IPv6 link-local address, unless it is known by other means that the remote system will not sendRedirects.BFD Echo packets MUST be transmitted in such a way as to ensure that they are received by the remote system. On multiaccess media, forexample, this requires that the destination datalink addresscorresponds to the remote system.The above requirements may require the bypassing of some common IPlayer functionality, particularly in host implementations.5. TTL/Hop Limit IssuesIf BFD authentication is not in use on a session, all BFD Controlpackets for the session MUST be sent with a Time to Live (TTL) or Hop Limit value of 255. All received BFD Control packets that aredemultiplexed to the session MUST be discarded if the received TTL or Hop Limit is not equal to 255. A discussion of this mechanism can be found in [GTSM].If BFD authentication is in use on a session, all BFD Control packets MUST be sent with a TTL or Hop Limit value of 255. All received BFD Control packets that are demultiplexed to the session MAY bediscarded if the received TTL or Hop Limit is not equal to 255. Ifthe TTL/Hop Limit check is made, it MAY be done before anycryptographic authentication takes place if this will avoidunnecessary calculation that would be detrimental to the receivingsystem.In the context of this section, "authentication in use" means thatthe system is sending BFD Control packets with the Authentication bit set and with the Authentication Section included and that allunauthenticated packets demultiplexed to the session are discarded,per the BFD base specification.Katz & Ward Standards Track [Page 4]6. Addressing IssuesImplementations MUST ensure that all BFD Control packets aretransmitted over the one-hop path being protected by BFD.On a multiaccess network, BFD Control packets MUST be transmittedwith source and destination addresses that are part of the subnet(addressed from and to interfaces on the subnet).On a point-to-point link, the source address of a BFD Control packet MUST NOT be used to identify the session. This means that theinitial BFD packet MUST be accepted with any source address, and that subsequent BFD packets MUST be demultiplexed solely by the YourDiscriminator field (as is always the case). This allows the source address to change if necessary. If the received source addresschanges, the local system MUST NOT use that address as thedestination in outgoing BFD Control packets; rather, it MUST continue to use the address configured at session creation. An implementation MAY notify the application that the neighbor’s source address haschanged, so that the application might choose to change thedestination address or take some other action. Note that the TTL/Hop Limit check described in section 5 (or the use of authentication)precludes the BFD packets from having come from any source other than the immediate neighbor.7. BFD for Use with TunnelsA number of mechanisms are available to tunnel IPv4 and IPv6 overarbitrary topologies. If the tunnel mechanism does not decrement the TTL or Hop Limit of the network protocol carried within, themechanism described in this document may be used to provide liveness detection for the tunnel. The BFD authentication mechanism SHOULD be used and is strongly encouraged.8. IANA ConsiderationsPorts 3784 and 3875 were assigned by IANA for use with the BFDControl and BFD Echo protocols, respectively.9. Security ConsiderationsIn this application, the use of TTL=255 on transmit and receive,coupled with an association to an incoming interface, is viewed assupplying equivalent security characteristics to other protocols used in the infrastructure, as it is not trivially spoofable. Thesecurity implications of this mechanism are further discussed in[GTSM].Katz & Ward Standards Track [Page 5]The security implications of the use of BFD authentication arediscussed in [BFD].The use of the TTL=255 check simultaneously with BFD authenticationprovides a low overhead mechanism for discarding a class ofunauthorized packets and may be useful in implementations in whichcryptographic checksum use is susceptible to denial-of-serviceattacks. The use or non-use of this mechanism does not impactinteroperability.10. References10.1. Normative References[BFD] Katz, D. and D. Ward, "Bidirectional ForwardingDetection", RFC 5880, June 2010.[BFD-GENERIC] Katz, D. and D. Ward, "Generic Application ofBidirectional Forwarding Detection (BFD)", RFC 5882,June 2010.[GTSM] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. Pignataro, "The Generalized TTL Security Mechanism(GTSM)", RFC 5082, October 2007.[KEYWORDS] Bradner, S., "Key words for use in RFCs to IndicateRequirement Levels", BCP 14, RFC 2119, March 1997.10.2. Informative References[BCP38] Ferguson, P. and D. Senie, "Network Ingress Filtering: Defeating Denial of Service Attacks which employ IPSource Address Spoofing", BCP 38, RFC 2827, May 2000.[TFRC] Floyd, S., Handley, M., Padhye, J., and J. Widmer, "TCP Friendly Rate Control (TFRC): Protocol Specification", RFC 5348, September 2008.Katz & Ward Standards Track [Page 6]Authors’ AddressesDave KatzJuniper Networks1194 N. Mathilda Ave.Sunnyvale, CA 94089-1206USAPhone: +1-408-745-2000EMail: dkatz@Dave WardJuniper Networks1194 N. Mathilda Ave.Sunnyvale, CA 94089-1206USAPhone: +1-408-745-2000EMail: dward@Katz & Ward Standards Track [Page 7]。

中国电信家庭网关与增强型终端综合管理系统接口技术要求

中国电信集团公司 2009年3月中国电信集团公司技术标准 Q/CT 2271-2013中国电信家庭网关与增强型终端综合管理系统接口技术要求 Technical Specification of Interface between HGW and ITMS+ of China Telecom 2013-02发布 2013-02实施中国电信集团公司发布目次前言...................................................................................................................................................................... V II 中国电信家庭网关与增强型终端综合管理系统接口技术要求 .. (1)1 范围 (1)2 规范性引用文件 (1)3 缩略语 (1)4 家庭网关与ITMS+接口总体概述 (4)4.1 家庭网关与ITMS+接口在网络中的位置 (4)4.2 家庭网关与ITMS+接口主要内容 (4)5 接口技术要求 (4)5.1 家庭网关与ITMS+接口框架 (4)5.1.1 家庭网关与ITMS+接口描述图 (4)5.1.2 家庭网关与ITMS+接口定义 (5)5.1.3 终端管理协议栈分层模型 (5)5.2 RPC方法概述 (6)5.3 家庭网关与ITMS+接口安全 (7)5.3.1 家庭网关发起的安全连接流程 (7)5.3.2 ITMS+发起的安全连接流程 (8)5.4 家庭网关与设备认证注册接口（M1） (9)5.4.1 M1接口描述图 (9)5.4.2 首次连接设备认证接口（基于物理ID） (9)5.4.3 首次连接设备认证接口（基于逻辑ID） (12)5.4.4 非首次连接设备认证接口 (15)5.5 家庭网关与参数监视接口模块（M2） (15)5.5.1 M2接口描述图 (15)5.5.2 参数模型获取接口 (16)5.5.3 参数查询接口 (17)5.5.4 参数变化上报接口 (18)5.6 家庭网关与参数配置接口模块（M3） (19)5.6.1 M3接口描述图 (19)5.6.2 参数属性上报接口 (19)5.6.3 配置用户可写属性接口 (20)5.6.4 参数实例配置接口（SetParameterValues） (21)5.6.5 实例删除配置接口 (22)5.6.6 参数实例配置接口（配置文件） (23)5.6.7 上传配置文件接口 (24)5.6.8 上传日志文件接口 (26)5.6.9 配置电信维护帐号接口 (27)5.6.10 设备告警接口 (28)5.6.11 设备监控接口 (29)5.7 家庭网关与软件升级接口模块（M4） (30)5.7.1 M4接口描述图 (30)5.7.2 软件升级接口 (31)5.7.3 软件版本查询接口 (33)5.7.4 软件升级配置备份接口 (34)5.8 家庭网关与测试诊断接口模块（M5） (37)5.8.1 M5接口描述图 (37)5.8.2 PING测试接口 (37)5.8.3 ATMF5Loop测试接口 (39)5.8.4 重启接口 (41)5.8.5 恢复出厂设置接口 (42)5.8.6 DSL测试接口 (43)5.8.7 IAD模块测试接口 (45)5.9 机卡分离型家庭网关与设备认证注册接口（M1） (47)5.9.1 M1接口描述图 (47)5.9.2 首次连接设备认证接口 (47)5.9.3 非首次连接设备认证接口 (50)附录A （规范性附录）RPC方法定义 (52)A.1 Inform (52)A.2 Inform eventCodes (53)附录B（规范性附录）RPC XML Schema描述 (54)B.1 XML Schema文件头 (54)B.2 SOAP信包头 (54)B.3 SOAP错误代码 (54)B.4 RPC参数类型定义 (54)B.5 RPC方法请求/响应 (55)附录C （规范性附录）业务配置描述 (58)C.1业务配置逻辑图 (58)C.2 业务配置模板 (58)C.2.1 基础类配置模板 (58)C.2.1.3 DDNS (61)C.2.1.4 WLAN (62)C.2.1.5 家庭网关电信维护帐号管理 (64)C.2.1.6 TR-069 (64)C.2.1.7 强制家庭门户管理 (64)C.2.1.8 PORT FORWARDING (64)C.2.1.9 DHCP SERVER (64)C.2.1.10 ALG功能开关 (65)C.2.1.11断线重连功能 (66)C.2.1.12网络服务管理 (66)C.2.1.13 LAN 上行 (66)C.2.1.14 QOS (67)C.2.1.15 日志管理 (68)C.2.1.16 快速恢复 (68)C.2.1.17 中间件平台管理 (69)C.2.1.18 用户信息管理 (69)C.2.1.19设备告警 (70)C.2.1.20状态监视 (70)C.2.1.21 EPON上行 (71)C.2.1.22 UPNP功能启用 (72)C.2.1.23 VDSL2上行 (72)C.2.1.24 IPv6功能启用 (73)C.2.1.25 GPON上行 (73)C.2.1.26 DHCPv4网络侧OPTION60功能 (74)C.2.1.27 DHCPv4网络侧OPTION125功能 (75)C.2.1.28 Ping功能 (75)C.2.1.29 家庭网关卡 (76)C.2.1.30 DHCPv6 OPTION16功能 (76)C.2.1.31 DHCPv6 OPTION17功能 (77)C.2.1.32 WAN连接索引 (77)C.2.1.33 家庭网关能力信息 (78)C.2.1.34 时间服务器配置信息 (79)C.2.1.35 VLAN绑定关系 (80)C.2.1.36 DLNA信息 (81)C.2.1.39全路由模式 (82)C.2.2 面向应用配置 (83)C.2.2.1 VoIP (83)C.2.2.2 IPTV (91)C.2.2.3 多终端上网 (91)C.2.3 IPv6相关配置 (92)C.2.3.1 WAN IPConnectionIPv6地址配置 (92)C.2.3.2 WAN PPPConnectionIPv6地址配置 (93)C.2.3.3 LAN 管理地址配置 (93)C.2.3.4 LAN IPv6 全局配置 (94)C.2.3.4 LAN IPv6 DHCPv6 Server配置 (94)C.2.3.5 LAN RADVD配置 (94)C.2.3.6 DS-lite功能参数 (95)附录D（规范性附录）对TR-069的扩展 (96)D.1 RPC方法 (96)D.2 RPC方法修订清单 (96)附录E （规范性附录）设备告警信息 (98)附录F (规范性附录) 家庭网关和ITMS+交互约定细则 (99)F.1家庭网关TR-069参数树初始配置技术细则 (99)F.2 ADSL上联桥连接建立流程 (99)F.3 ADSL上联路由IPv4连接建立流程 (100)F.4 LAN上联桥连接建立流程 (100)F.5 LAN上联路由IPv4连接建立流程 (101)F.6 家庭网关和ITMS+交互过程重启原则 (101)F.7 家庭网关Inform消息上报，参数列表扩充 (101)F.8 ITMS+与家庭网关交互约定 (101)F.9 ITMS+异常流程 (102)F.10 ITMS+对家庭网关远程升级流程（配置文件不兼容） (102)F.11平台业务下发逻辑判断 (102)F.12 VOIP业务发放流程 (102)F.13无线加密建立流程 (104)F.14端口映射建立流程 (104)F.15 QOS出厂配置模版示例 (105)F.16 QOS建立流程 (105)F.17 ADSL上联DHCPv4方式建立流程 (106)F.18 LAN上联DHCP方式建立流程 (106)F.19 ADSL上联Static IP方式建立流程 (106)F.20 LAN上联Static IP方式建立流程 (107)F.21 ITMS+与家庭网关通信超时控制建议 (108)F.22基于逻辑ID的设备首次认证流程 (109)F.23基于DSCP数据标识优先级队列方式的QoS保障建立流程（示例） (109)F.24基于目的IP优先级队列方式的QoS保障建立流程（示例） (110)F.25基于业务发现优先级队列方式的QoS保障建立流程1（示例） (110)F.26基于业务发现优先级队列方式的QoS保障建立流程2（示例） (111)F.27 EPON上联桥连接建立流程 (111)F.28 EPON上联路由IPv4连接建立流程 (111)F.29 EPON上联DHCv4方式建立流程 (112)F.30 EPON上联Static IP方式建立流程 (112)F.31 ITMS+下发业务模板示例 (113)F.32 VDSL2上联桥连接建立流程 (113)F.33 VDSL2上联路由IPv4连接建立流程 (114)F.34 VDSL2上联DHCPv4方式建立流程 (114)F.35 VDSL2上联Static IP方式建立流程 (115)F.36 GPON上联桥连接建立流程 (115)F.37 GPON上联路由IPv4连接建立流程 (116)F.38 GPON上联DHCPv4方式建立流程 (116)F.39 GPON上联Static IP方式建立流程 (117)F.40家庭网关通过DHCP OPTION60/DHCPv6 OPTION16上报语音账号流程 (117)F.41 ADSL上联IPv6 路由连接建立流程 (118)F.42 ADSL上联DHCPv6方式建立流程 (119)F.43 LAN上联IPv6路由连接建立流程 (120)F.44 LAN上联DHCPv6方式建立流程 (120)F.45 EPON上联IPv6路由连接建立流程 (121)F.46 EPON上联DHCPv6方式建立流程 (122)F.47 VDSL2上联IPv6路由连接建立流程 (122)F.48 VDSL2上联DHCPv6方式建立流程 (123)F.49 GPON上联IPv6路由连接建立流程 (124)F.50 GPON上联DHCPv6方式建立流程 (124)F.51 ITMS+对不同版本家庭网关配置流程建议 (125)F.52 IPv6家庭网关LAN侧配置流程 (125)F.53机卡分离型家庭网关相关流程补充 (125)前言本标准按照GB/T 1.1-2009给出的规则起草。

和SIP有关的RFC

RFC 3666 SIP Public Switched Telephone Network (PSTN) Call Flows.
RFC 3680 SIP Event Package for Registrations
RFC 3702 Authentication, Authorization, and Accounting Requirements for the SIP
RFC 3515 The Session Initiation Protocol (SIP) Refer Method
RFC 3578 Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the SIP
RFC 4244 An Extension to the SIP for Request History Information
RFC 4245 High-Level Requirements for Tightly Coupled SIP Conferencing
RFC 4320 Actions Addressing Identified Issues with the SIP's Non-INVITE Transaction
RFC 3581 An Extension to the SIP for Symmetric Response Routing
RFC 3603 Private SIP Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture.

rfc5288.AES Galois Counter Mode (GCM) Cipher Suites for TLS

Network Working Group J. Salowey Request for Comments: 5288 A. Choudhury Category: Standards Track D. McGrew Cisco Systems, Inc. August 2008 AES Galois Counter Mode (GCM) Cipher Suites for TLSStatus of This MemoThis document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions forimprovements. Please refer to the current edition of the "InternetOfficial Protocol Standards" (STD 1) for the standardization stateand status of this protocol. Distribution of this memo is unlimited.AbstractThis memo describes the use of the Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM) as a Transport Layer Security (TLS)authenticated encryption operation. GCM provides bothconfidentiality and data origin authentication, can be efficientlyimplemented in hardware for speeds of 10 gigabits per second andabove, and is also well-suited to software implementations. Thismemo defines TLS cipher suites that use AES-GCM with RSA, DSA, andDiffie-Hellman-based key exchange mechanisms.Table of Contents1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 22. Conventions Used in This Document . . . . . . . . . . . . . . . 23. AES-GCM Cipher Suites . . . . . . . . . . . . . . . . . . . . . 24. TLS Versions . . . . . . . . . . . . . . . . . . . . . . . . . 35. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 46. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6.1. Counter Reuse . . . . . . . . . . . . . . . . . . . . . . . 46.2. Recommendations for Multiple Encryption Processors . . . . 47. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 58. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 Salowey, et al. Standards Track [Page 1]1. IntroductionThis document describes the use of AES [AES] in Galois Counter Mode(GCM) [GCM] (AES-GCM) with various key exchange mechanisms as acipher suite for TLS. AES-GCM is an authenticated encryption withassociated data (AEAD) cipher (as defined in TLS 1.2 [RFC5246])providing both confidentiality and data origin authentication. Thefollowing sections define cipher suites based on RSA, DSA, andDiffie-Hellman key exchanges; ECC-based (Elliptic Curve Cryptography) cipher suites are defined in a separate document [RFC5289].AES-GCM is not only efficient and secure, but hardwareimplementations can achieve high speeds with low cost and lowlatency, because the mode can be pipelined. Applications thatrequire high data throughput can benefit from these high-speedimplementations. AES-GCM has been specified as a mode that can beused with IPsec ESP [RFC4106] and 802.1AE Media Access Control (MAC) Security [IEEE8021AE].2. Conventions Used in This DocumentThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].3. AES-GCM Cipher SuitesThe following cipher suites use the new authenticated encryptionmodes defined in TLS 1.2 with AES in Galois Counter Mode (GCM) [GCM]: CipherSuite TLS_RSA_WITH_AES_128_GCM_SHA256 = {0x00,0x9C}CipherSuite TLS_RSA_WITH_AES_256_GCM_SHA384 = {0x00,0x9D}CipherSuite TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 = {0x00,0x9E}CipherSuite TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 = {0x00,0x9F}CipherSuite TLS_DH_RSA_WITH_AES_128_GCM_SHA256 = {0x00,0xA0}CipherSuite TLS_DH_RSA_WITH_AES_256_GCM_SHA384 = {0x00,0xA1}CipherSuite TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 = {0x00,0xA2}CipherSuite TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 = {0x00,0xA3}CipherSuite TLS_DH_DSS_WITH_AES_128_GCM_SHA256 = {0x00,0xA4}CipherSuite TLS_DH_DSS_WITH_AES_256_GCM_SHA384 = {0x00,0xA5}CipherSuite TLS_DH_anon_WITH_AES_128_GCM_SHA256 = {0x00,0xA6}CipherSuite TLS_DH_anon_WITH_AES_256_GCM_SHA384 = {0x00,0xA7}These cipher suites use the AES-GCM authenticated encryption withassociated data (AEAD) algorithms AEAD_AES_128_GCM andAEAD_AES_256_GCM described in [RFC5116]. Note that each of theseAEAD algorithms uses a 128-bit authentication tag with GCM (inparticular, as described in Section 3.5 of [RFC4366], theSalowey, et al. Standards Track [Page 2]"truncated_hmac" extension does not have an effect on cipher suitesthat do not use HMAC). The "nonce" SHALL be 12 bytes long consisting of two parts as follows: (this is an example of a "partiallyexplicit" nonce; see Section 3.2.1 in [RFC5116]).struct {opaque salt[4];opaque nonce_explicit[8];} GCMNonce;The salt is the "implicit" part of the nonce and is not sent in thepacket. Instead, the salt is generated as part of the handshakeprocess: it is either the client_write_IV (when the client issending) or the server_write_IV (when the server is sending). Thesalt length (SecurityParameters.fixed_iv_length) is 4 octets.The nonce_explicit is the "explicit" part of the nonce. It is chosen by the sender and is carried in each TLS record in theGenericAEADCipher.nonce_explicit field. The nonce_explicit length(SecurityParameters.record_iv_length) is 8 octets.Each value of the nonce_explicit MUST be distinct for each distinctinvocation of the GCM encrypt function for any fixed key. Failure to meet this uniqueness requirement can significantly degrade security. The nonce_explicit MAY be the 64-bit sequence number.The RSA, DHE_RSA, DH_RSA, DHE_DSS, DH_DSS, and DH_anon key exchanges are performed as defined in [RFC5246].The Pseudo Random Function (PRF) algorithms SHALL be as follows:For cipher suites ending with _SHA256, the PRF is the TLS PRF[RFC5246] with SHA-256 as the hash function.For cipher suites ending with _SHA384, the PRF is the TLS PRF[RFC5246] with SHA-384 as the hash function.Implementations MUST send TLS Alert bad_record_mac for all types offailures encountered in processing the AES-GCM algorithm.4. TLS VersionsThese cipher suites make use of the authenticated encryption withadditional data defined in TLS 1.2 [RFC5246]. They MUST NOT benegotiated in older versions of TLS. Clients MUST NOT offer thesecipher suites if they do not offer TLS 1.2 or later. Servers thatselect an earlier version of TLS MUST NOT select one of these cipher suites. Because TLS has no way for the client to indicate that it Salowey, et al. Standards Track [Page 3]supports TLS 1.2 but not earlier, a non-compliant server mightpotentially negotiate TLS 1.1 or earlier and select one of the cipher suites in this document. Clients MUST check the TLS version andgenerate a fatal "illegal_parameter" alert if they detect anincorrect version.5. IANA ConsiderationsIANA has assigned the following values for the cipher suites defined in this document:CipherSuite TLS_RSA_WITH_AES_128_GCM_SHA256 = {0x00,0x9C}CipherSuite TLS_RSA_WITH_AES_256_GCM_SHA384 = {0x00,0x9D}CipherSuite TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 = {0x00,0x9E}CipherSuite TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 = {0x00,0x9F}CipherSuite TLS_DH_RSA_WITH_AES_128_GCM_SHA256 = {0x00,0xA0}CipherSuite TLS_DH_RSA_WITH_AES_256_GCM_SHA384 = {0x00,0xA1}CipherSuite TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 = {0x00,0xA2}CipherSuite TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 = {0x00,0xA3}CipherSuite TLS_DH_DSS_WITH_AES_128_GCM_SHA256 = {0x00,0xA4}CipherSuite TLS_DH_DSS_WITH_AES_256_GCM_SHA384 = {0x00,0xA5}CipherSuite TLS_DH_anon_WITH_AES_128_GCM_SHA256 = {0x00,0xA6}CipherSuite TLS_DH_anon_WITH_AES_256_GCM_SHA384 = {0x00,0xA7}6. Security ConsiderationsThe security considerations in [RFC5246] apply to this document aswell. The remainder of this section describes securityconsiderations specific to the cipher suites described in thisdocument.6.1. Counter ReuseAES-GCM security requires that the counter is never reused. The IVconstruction in Section 3 is designed to prevent counter reuse.Implementers should also understand the practical considerations ofIV handling outlined in Section 9 of [GCM].6.2. Recommendations for Multiple Encryption ProcessorsIf multiple cryptographic processors are in use by the sender, thenthe sender MUST ensure that, for a particular key, each value of the nonce_explicit used with that key is distinct. In this case, eachencryption processor SHOULD include, in the nonce_explicit, a fixedvalue that is distinct for each processor. The recommended format is nonce_explicit = FixedDistinct || VariableSalowey, et al. Standards Track [Page 4]where the FixedDistinct field is distinct for each encryptionprocessor, but is fixed for a given processor, and the Variable field is distinct for each distinct nonce used by a particular encryptionprocessor. When this method is used, the FixedDistinct fields usedby the different processors MUST have the same length.In the terms of Figure 2 in [RFC5116], the Salt is the Fixed-Commonpart of the nonce (it is fixed, and it is common across allencryption processors), the FixedDistinct field exactly correspondsto the Fixed-Distinct field, the Variable field corresponds to theCounter field, and the explicit part exactly corresponds to thenonce_explicit.For clarity, we provide an example for TLS in which there are twodistinct encryption processors, each of which uses a one-byteFixedDistinct field:Salt = eedc68dcFixedDistinct = 01 (for the first encryption processor) FixedDistinct = 02 (for the second encryption processor)The GCMnonces generated by the first encryption processor, and their corresponding nonce_explicit, are:GCMNonce nonce_explicit------------------------ ----------------------------eedc68dc0100000000000000 0100000000000000eedc68dc0100000000000001 0100000000000001eedc68dc0100000000000002 0100000000000002...The GCMnonces generated by the second encryption processor, and their corresponding nonce_explicit, areGCMNonce nonce_explicit------------------------ ----------------------------eedc68dc0200000000000000 0200000000000000eedc68dc0200000000000001 0200000000000001eedc68dc0200000000000002 0200000000000002...7. AcknowledgementsThis document borrows heavily from [RFC5289]. The authors would like to thank Alex Lam, Simon Josefsson, and Pasi Eronen for providinguseful comments during the review of this document.Salowey, et al. Standards Track [Page 5]8. References8.1. Normative References[AES] National Institute of Standards and Technology,"Advanced Encryption Standard (AES)", FIPS 197,November 2001.[GCM] Dworkin, M., "Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC",National Institute of Standards and Technology SP 800- 38D, November 2007.[RFC2119] Bradner, S., "Key words for use in RFCs to IndicateRequirement Levels", BCP 14, RFC 2119, March 1997.[RFC5116] McGrew, D., "An Interface and Algorithms forAuthenticated Encryption", RFC 5116, January 2008.[RFC5246] Dierks, T. and E. Rescorla, "The Transport LayerSecurity (TLS) Protocol Version 1.2", RFC 5246,August 2008.8.2. Informative References[IEEE8021AE] Institute of Electrical and Electronics Engineers,"Media Access Control Security", IEEE Standard 802.1AE, August 2006.[RFC4106] Viega, J. and D. McGrew, "The Use of Galois/CounterMode (GCM) in IPsec Encapsulating Security Payload(ESP)", RFC 4106, June 2005.[RFC4366] Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J., and T. Wright, "Transport Layer Security (TLS)Extensions", RFC 4366, April 2006.[RFC5289] Rescorla, E., "TLS Elliptic Curve Cipher Suites withSHA-256/384 and AES Galois Counter Mode", RFC 5289,August 2008.Salowey, et al. Standards Track [Page 6]Authors’ AddressesJoseph SaloweyCisco Systems, Inc.2901 3rd. AveSeattle, WA 98121USAEMail: jsalowey@Abhijit ChoudhuryCisco Systems, Inc.3625 Cisco WaySan Jose, CA 95134USAEMail: abhijitc@David McGrewCisco Systems, Inc.170 W Tasman DriveSan Jose, CA 95134USAEMail: mcgrew@Salowey, et al. Standards Track [Page 7]Full Copyright StatementCopyright (C) The IETF Trust (2008).This document is subject to the rights, licenses and restrictionscontained in BCP 78, and except as set forth therein, the authorsretain all their rights.This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual PropertyThe IETF takes no position regarding the validity or scope of anyIntellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described inthis document or the extent to which any license under such rightsmight or might not be available; nor does it represent that it hasmade any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can befound in BCP 78 and BCP 79.Copies of IPR disclosures made to the IETF Secretariat and anyassurances of licenses to be made available, or the result of anattempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of thisspecification can be obtained from the IETF on-line IPR repository at /ipr.The IETF invites any interested party to bring to its attention anycopyrights, patents or patent applications, or other proprietaryrights that may cover technology that may be required to implementthis standard. Please address the information to the IETF atietf-ipr@.Salowey, et al. Standards Track [Page 8]。

ONVIF20协议中文原版

协议原版目录1 范围 ................................................................................................................. 错误!未定义书签。

2 引用标准 ......................................................................................................... 错误!未定义书签。

3 术语与定义 ..................................................................................................... 错误!未定义书签。

定义 ..................................................................................................................... 错误!未定义书签。

缩写....................................................................................................................... 错误!未定义书签。

4 概述................................................................................................................. 错误!未定义书签。

W EB 服务............................................................................................................. 错误!未定义书签。

rfc2578 mib标准

rfc2578 mib标准RFC 2578是一项关于Management Information Base（MIB）标准的RFC（Request for Comments）文件。

MIB是一种用于管理网络设备的协议，它定义了网络设备所支持的操作和属性。

RFC 2578定义了一个通用的MIB模块，用于支持基于SNMP （Simple Network Management Protocol）的网络管理。

SNMP是一种用于收集和管理网络设备信息的协议，它通过MIB来提供设备的管理信息。

MIB是一种树状结构，其中包含了有关设备的各种属性和操作。

它使用了一种简单的语法来描述设备的特征，从而使管理者能够通过网络获取设备的信息并进行管理。

RFC 2578定义了一组通用的MIB对象，它们可以应用于任何类型的设备。

这些对象包括通用的网络管理对象，如设备的名称、描述、类型等，以及特定于某些设备类型的对象，如CPU利用率、内存使用情况等。

RFC 2578还定义了MIB的编码规则和格式。

其中，MIB使用ASN.1（Abstract Syntax Notation One）来定义数据类型和数据结构。

ASN.1是一种用于描述数据结构和编码规则的语言，它将数据结构定义为一个抽象的语法，不依赖于具体的编程语言。

MIB的数据编码使用了基于SNMP的BER（Basic Encoding Rules）规范。

BER定义了一种二进制编码格式，用于在网络上传输MIB数据。

这种编码格式具有可扩展性和兼容性，可以适应不同的网络环境和设备类型。

RFC 2578还介绍了MIB的管理和使用。

它定义了一种基于SNMP的网络管理架构，包括管理站点、代理站点和被管理的设备。

管理者可以通过SNMP协议向代理站点发送命令或查询，代理站点则通过管理MIB来执行命令或返回查询结果。

总结起来，RFC 2578是一项关于MIB标准的RFC文件，它定义了MIB的结构、编码和使用规范。

rfc相关设置及使用

rfc相关设置及使用摘要：一、RFC简介1.RFC的含义2.RFC的作用二、RFC相关设置1.RFC文件的存放位置2.RFC文件的命名规则3.RFC文件的权限设置三、RFC的使用方法1.RFC文件的查看2.RFC文件的编辑3.RFC文件的导入导出四、RFC的高级应用1.RFC模板的使用2.RFC文件的版本控制3.RFC与其他软件的协同工作正文：RFC（Request for Comments）是一种广泛应用于计算机领域的文档格式，它主要用于记录和共享各种计算机网络协议和技术规范。

作为一个重要的知识库，RFC对于网络工程师、程序员等IT从业者来说具有很高的参考价值。

本文将为您详细介绍RFC的相关设置及使用方法。

首先，我们需要了解RFC的基本概念。

RFC（Request for Comments）意为“请求评论”，是一种用于记录和共享计算机网络协议和技术规范的文档格式。

它起源于20世纪60年代的美国，如今已成为互联网领域最重要的知识库之一。

RFC文件通常由网络工程师、程序员等IT从业者编写，并经过专家评审和公开讨论，以确保其内容的准确性和可靠性。

接下来，我们来了解RFC相关设置。

RFC文件的存放位置通常在系统的“/etc/rfc”目录下。

文件的命名规则一般采用“RFC”加数字的形式，如“RFC1925”。

此外，文件的权限设置也很重要，一般来说，RFC文件应具有可读、可写和可执行的权限，以便于用户查看、编辑和执行。

在了解RFC的相关设置后，我们来学习RFC的使用方法。

首先，可以通过命令行或图形界面查看RFC文件的内容。

编辑RFC文件时，可以使用文本编辑器或专门的RFC编辑工具。

此外，RFC文件还可以导入导出，方便与其他软件协同工作。

在掌握RFC的基本使用方法后，我们可以进一步探索RFC的高级应用。

RFC模板可以帮助用户快速创建和编辑RFC文件。

此外，RFC文件还支持版本控制，可以方便地追踪文件的变更历史。

IBM Cognos Transformer V11.0 用户指南说明书

Dimensional Modeling Workflow................................................................................................................. 1 Analyzing Your Requirements and Source Data.................................................................................... 1 Preprocessing Your ...................................................................................................................... 2 Building a Prototype............................................................................................................................... 4 Refining Your Model............................................................................................................................... 5 Diagnose and Resolve Any Design Problems........................................................................................ 6

交换机命令配置手册北京博维

用户管理.........................6 PING 诊断功能.......................................................................................................................... 6 Ping 功能简介......................................................................................................................6 Ping 相关命令......................................................................................................................6
工业以太网交换机命令行配置手册
1
目
第1章 1.1 1.2 1.2.1 1.2.2 1.2.3 1.2.4 第2章 2.1 2.1.1 2.1.2 2.1.3 2.2 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.2 2.4.3 2.4.4 第3章 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 第4章 4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2
系统软件管理...................................................................................................................... 4 配置文件管理...................................................................................................................... 4 典型配置举例...................................................................................................................... 4

ipmi maximum number of sessions already in use

ipmi maximum number of sessions already in use
IPMI是一种远程管理系统，它通过网络连接到服务器，可以对服务器进行监控和管理。

在使用IPMI时，我们需要通过Web界面或命令行界面来与服务器进行交互。

但是，IPMI有一个最大会话数的限制，当达到这个限制时，我们就无法再与服务器进行交互。

那么，为什么会出现IPMI最大会话数已经被使用的情况呢？其实，这主要是由于IPMI的工作原理所决定的。

IPMI通过启动一个会话来与服务器进行交互。

当我们使用IPMI 与服务器交互时，会话就会被建立。

如果会话的数量超过了IPMI的最大会话数，那么就无法再建立新的会话了。

这就是IPMI最大会话数已经被使用的情况。

那么，如何解决这个问题呢？最简单的方法就是关闭一些闲置的会话。

通过Web界面或命令行界面，我们可以查看当前建立的会话数，并关闭一些闲置的会话。

另外，我们还可以增加IPMI的最大会话数来解决这个问题。

但是，需要注意的是，增加最大会话数可能会对服务器的性能产生一定的影响，因此应该根据具体情况来决定是否需要增加最大会话数。

总的来说，IPMI最大会话数已经被使用是一个比较常见的问题，但是通过合理的管理和设置，我们可以很容易地解决这个问题。

在使用IPMI时，我们应该注意会话的数量，及时关闭闲置的会话，并根据需要增加最大会话数。

这样，我们就可以更好地利用IPMI进行服务器的远程管理和监控。

rfc5168.XML Schema for Media Control

机顶盒与IPTV业务运营平台接口技术规范V2.2(EPG部分)

中移动家庭网关终端技术规范v3.0.0

直连sap rfc 参数结构

机顶盒与IPTV业务运营平台接口技术规范V2.2(EPG部分)

5616 网络风暴抑制

{业务管理}网络短消息业务技术要求精编

[生活]计算机专业英语词汇缩写大全

rfc相关设置及使用

rfc5881.Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)

中国电信家庭网关与增强型终端综合管理系统接口技术要求

和SIP有关的RFC

rfc5288.AES Galois Counter Mode (GCM) Cipher Suites for TLS

ONVIF20协议中文原版

rfc2578 mib标准

rfc相关设置及使用

IBM Cognos Transformer V11.0 用户指南说明书

交换机命令配置手册 北京博维

ipmi maximum number of sessions already in use

交换机命令配置手册北京博维