rfc3716.The IETF in the Large Administration and Execution

格式：pdf
大小：58.33 KB
文档页数：40

下载文档原格式

因特网流协议

IPv4在IETF于1981年9月发布的RFC 791中被描述，此RFC替换了于1980年1月发布的RFC 760。
IPv4是一种无连接的协议，操作在使用分组交换的链路层（如以太）上。此协议会尽最大努力交付数据包，意即它不保证任何数据包均能送达目的地，也不保证所有数据包均按照正确的顺序无重复地到达。这些方面是由上层的传输协议（如传输控制协议）处理的。
谢谢观看
服务质量
服务质量（英语：Quality of Service，缩写QoS）是一个术语，在分组交换络领域中指络满足给定业务合同的概率；或在许多情况下，非正式地指分组在络中两点间通过的概率。QoS是一种控制机制，它提供了针对不同用户或者不同数据流采用相应不同的优先级，或者是根据应用程序的要求，保证数据流的性能达到一定的水准。QoS的保证对于容量有限的络来说是十分重要的，特别是对于流多媒体应用，例如VoIP和IPTV等，因为这些应用常常需要固定的传输率，对延时也比较敏感。
在业务领域中，服务质量是指线路噪音和声音，适当的音量水平等指标的衡量，并且不能与服务等级相混淆。
实质上有两种方式提供QoS保证。第一种，就是简单地提供大量的资源，用丰富、安全的余量设备应付预期中的“高峰”需求。这样既好又简单，然而有人认为这种方式代价昂贵，而且不能应对高峰需求超越预期的情形，部署额外的资源也很耗费时间。
第二种是要求用户预约带宽，并且仅在能够提供可靠服务的前提下接受预约。自然，可以为预约服务向用户收费。常用的实现方法有两类。
IPv4
IPv4
际协议版本4（英语：InternetProtocolversion4，IPv4），又称互联通信协议第四版，是际协议开发过程中的第四个修订版本，也是此协议第一个被广泛部署的版本。IPv4是互联的核心，也是使用最广泛的际协议版本，其后继版本为IPv6，直到2011年，IANAIPv4位址完全用尽时，IPv6仍处在部署的初期。

IPv6 演进技术要求基于 IPv6 段路由(SRv6)的 IP 承载网络-最新国标

IPv6演进技术要求第2部分：基于IPv6段路由(SRv6)的IP承载网络1 范围本文件规定了基于SRv6的IP承载网络总体架构、基于SRv6的设备层技术要求及基于SRv6的管控层技术要求。

本文件适用于支持SRv6的IP承载网络。

2 规范性引用文件下列文件中的内容通过文中的规范性引用而构成本文件必不可少的条款。

其中，注日期的引用文件，仅该日期对应的版本适用于本文件；不注日期的引用文件，其最新版本（包括所有的修改单）适用于本文件。

IETF RFC2493 IPv6规范中的通用报文隧道（Generic Packet Tunneling in IPv6 Specification）IETF RFC4659 IPv6 VPN场景中的BGP-MPLS IP虚拟私有网络扩展（BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN）IETF RFC5549 通告带有IPv6下一跳地址的IPv4网络层可达性信息（Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop）IETF RFC6437 IPv6流标签规范（IPv6 Flow Label Specification）IETF RFC6514 MPLS/BGP IP VPN中提供组播服务的BGP编码与处理（BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs）IETF RFC7432 基于BGP MPLS的EVPN（BGP MPLS-Based Ethernet VPN）IETF RFC7606 改进的BGP更新消息的错误处理（Revised Error Handling for BGP UPDATE Messages）IETF RFC8200 互联网协议第六版规范（Internet Protocol, Version 6 (IPv6) Specification）IETF RFC8402 分段路由架构（Segment Routing Architecure）IETF RFC8754 IPv6段路由报头(IPv6 Segment Routing Header)IETF RFC8986 SRv6网络编程（Segment Routing over IPv6 (SRv6) Network Programming）IETF RFC9252 基于SRv6的BGP overlay业务(BGP Overlay Services Based on Segment Routing over IPv6 (SRv6))IETF RFC9352 支持SRv6的ISIS扩展(IS-IS Extensions to Support Segment Routing over the IPv6 Data Plane）GB/T XXXXX IPv6演进技术要求第4部分：基于IPv6段路由(SRv6)的网络编程GB/T XXXXX IPv6演进技术要求第7部分：基于IPv6段路由(SRv6)的业务链GB/T XXXXX IPv6演进技术要求第8部分：基于IPv6段路由(SRv6)的报文头压缩GB/T XXXXX IPv6演进技术要求第9部分：基于IPv6段路由(SRv6)的网络故障保护3 术语、定义和缩略语3.1 术语和定义下列术语和定义适用于本文件。

中移动家庭网关终端技术规范v ()

中国移动通信企业标准家庭网关终端技术规范版本号：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目录2.规范性引用文件...............................................................................................................................3.术语、定义和缩略语 .......................................................................................................................4.设备总体定义...................................................................................................................................4.1.设备在网络中的位置 ....................................................................................................................4.2.接口定义........................................................................................................................................4.3.设备类型........................................................................................................................................5.接入型家庭网关...............................................................................................................................5.1.接口要求........................................................................................................................................网络侧接口........................................................................................................................................网络侧接口描述............................................................................................................................................网络侧以太网接口要求................................................................................................................................PON接口要求.................................................................................................................................................TD-SCDMA接口要求.......................................................................................................................................TD-LTE接口要求...........................................................................................................................................用户侧接口........................................................................................................................................用户侧以太网接口要求................................................................................................................................WLAN接口 ......................................................................................................................................................USB接口（可选）.........................................................................................................................................5.2.功能要求........................................................................................................................................数据通信要求....................................................................................................................................IP协议要求 ..................................................................................................................................................数据转发功能要求........................................................................................................................................DNS功能要求.................................................................................................................................................IPv4地址管理及拨号管理功能要求 ...........................................................................................................IPv6地址管理及拨号管理功能要求 ...........................................................................................................IPv4NAT要求.................................................................................................................................................ALG要求 ........................................................................................................................................................组播要求 .......................................................................................................................................................其他功能要求................................................................................................................................................安全要求............................................................................................................................................防火墙 ...........................................................................................................................................................登陆WEB页面的安全要求............................................................................................................................设备安全性 ...................................................................................................................................................QoS要求.............................................................................................................................................VLAN功能要求...................................................................................................................................USB扩展及管理（可选）.................................................................................................................设备发现要求....................................................................................................................................UPnP ...............................................................................................................................................................DLNA（可选）................................................................................................................................................支持WLAN的开启和禁用..............................................................................................................................基本要求 .......................................................................................................................................................多SSID要求 .................................................................................................................................................WLAN安全要求...............................................................................................................................................5WLANQoS要求...............................................................................................................................................WPS要求 ........................................................................................................................................................ 基本应用要求.....................................................................................................................................WLAN共享 ....................................................................................................................................................家庭存储（可选）........................................................................................................................................5.3.性能要求........................................................................................................................................ 路由转发性能要求............................................................................................................................吞吐量 ...........................................................................................................................................................地址学习 .......................................................................................................................................................缓存大小 .......................................................................................................................................................连接数量要求................................................................................................................................................ WLAN无线性能要求...........................................................................................................................WLAN吞吐量性能要求...................................................................................................................................WLAN覆盖性能要求.......................................................................................................................................WLAN接收灵敏度要求...................................................................................................................................5.4.管理和维护要求............................................................................................................................ 本地管理和配置要求........................................................................................................................本地管理基本要求........................................................................................................................................用户分级管理................................................................................................................................................系统信息管理................................................................................................................................................基本配置 .......................................................................................................................................................高级配置 .......................................................................................................................................................设备管理 .......................................................................................................................................................网络诊断 .......................................................................................................................................................设备认证注册功能........................................................................................................................................ 远程管理要求....................................................................................................................................远程管理基本要求........................................................................................................................................远程参数配置和性能监测............................................................................................................................远程故障诊断功能........................................................................................................................................设备告警功能................................................................................................................................................远程链路维持功能........................................................................................................................................软件远程管理................................................................................................................................................业务部署和控制............................................................................................................................................PON上行家庭网关远程管理实现方式 ......................................................................................................... 日志功能要求....................................................................................................................................5.5.预配置要求.................................................................................................................................... 预配置要求........................................................................................................................................5.6.硬件要求........................................................................................................................................ 基本要求............................................................................................................................................硬件基本框图示例............................................................................................................................5.7.软件要求........................................................................................................................................基本要求............................................................................................................................................软件基本架构....................................................................................................................................软件接口要求....................................................................................................................................用户登录要求....................................................................................................................................系统升级要求....................................................................................................................................5.8.配置界面要求................................................................................................................................配置界面要求....................................................................................................................................配置界面用户权限要求....................................................................................................................5.9.设备标识要求................................................................................................................................5.10.外观及附件要求..........................................................................................................................运营商Logo要求..............................................................................................................................设备标签要求....................................................................................................................................网关指示灯要求................................................................................................................................开关与按键要求................................................................................................................................设备面板标识要求............................................................................................................................设备接口要求....................................................................................................................................附件要求............................................................................................................................................5.11.运行环境要求..............................................................................................................................供电要求............................................................................................................................................环境要求............................................................................................................................................抗电磁干扰能力................................................................................................................................设备本身产生的电磁干扰要求........................................................................................................过压过流保护....................................................................................................................................5.12.认证要求......................................................................................................................................6.接入型家庭网关支持物联网功能 ....................................................................................................6.1.接入型家庭网关支持宜居通的功能要求（内置433M模块）...................................................433M模块要求...................................................................................................................................外围设备要求....................................................................................................................................业务功能描述....................................................................................................................................安防功能要求................................................................................................................................................家电控制功能................................................................................................................................................接入型家庭网关配置界面要求........................................................................................................配置界面要求................................................................................................................................................配置界面用户权限要求................................................................................................................................6.2.接入型家庭网关支持基于低功耗W I F I的物联网功能要求..........................................................设备接入功能要求............................................................................................................................WiFi接入.......................................................................................................................................................接入型家庭网关要求 ...............................................................................................................................外设要求...................................................................................................................................................DHCP流程要求 .............................................................................................................................................7.宽带应用型家庭网关 .......................................................................................................................7.1.类型描述..........................................................................................................................................7.2.分体机接入设备要求......................................................................................................................7.3.分体机应用设备（机顶盒）要求 ..................................................................................................硬件要求............................................................................................................................................硬件、接口及按键要求................................................................................................................................遥控器要求及参考设计................................................................................................................................电源要求 .......................................................................................................................................................配件要求 .......................................................................................................................................................设备标识要求................................................................................................................................................网络侧接口要求................................................................................................................................业务功能要求....................................................................................................................................互联网电视应用............................................................................................................................................多屏互动功能................................................................................................................................................概述...........................................................................................................................................................镜像功能...................................................................................................................................................分享功能...................................................................................................................................................家庭高清视频通话（可选）........................................................................................................................家庭卡拉OK功能（可选） .........................................................................................................................语音交互功能................................................................................................................................................软件要求............................................................................................................................................操作系统要求................................................................................................................................................软件协议要求................................................................................................................................................编码及解码能力要求....................................................................................................................................编解码能力要求 .......................................................................................................................................音视频播放质量要求 ...............................................................................................................................屏幕管理要求................................................................................................................................................防刷机要求 ...................................................................................................................................................管理要求............................................................................................................................................操作管理 .......................................................................................................................................................软件管理 .......................................................................................................................................................文件管理 .......................................................................................................................................................4.配置管理 ....................................................................................................................................................其他要求............................................................................................................................................供电要求 .......................................................................................................................................................环境要求 .......................................................................................................................................................噪声要求 .......................................................................................................................................................7.4.一体机设备要求............................................................................................................................网络侧接口要求................................................................................................................................网络接入功能要求............................................................................................................................业务功能要求....................................................................................................................................软件要求............................................................................................................................................管理要求............................................................................................................................................硬件要求............................................................................................................................................其他要求............................................................................................................................................供电要求 .......................................................................................................................................................环境要求 .......................................................................................................................................................噪声要求 .......................................................................................................................................................8.编制历史 .......................................................................................................................................... 附录A省公司代码.......................................................................................................................... 附录B设备故障消息（标准性附录） ...........................................................................................B.1告警编号规则 ...............................................................................................................................B.2设备告警信息列表 ....................................................................................................................... 附录C WIMO协议说明.....................................................................................................................C.1设备类型和功能流程 .....................................................................................................................C.2网络连接.........................................................................................................................................C.3设备连接.........................................................................................................................................C.4媒体格式要求.................................................................................................................................C.4.1视频编解码流程.....................................................................................................................C.4.2M-JPEG视频编解码方案.........................................................................................................C.4.3H.264视频编解码方案...........................................................................................................C.4.4音频编解码流程..................................................................................................................... 附录D手机遥控接口说明 ..............................................................................................................D.1设备发现.........................................................................................................................................D.2配对请求接口.................................................................................................................................D.3配对连接接口.................................................................................................................................D.4发送遥控器键值接口 .....................................................................................................................D.5发送文本接口.................................................................................................................................D.6发送心跳接口.................................................................................................................................D.7断开连接接口.................................................................................................................................D.8配对成功广播发送接口 .................................................................................................................D.9配对断开广播发送接口 ................................................................................................................. 附录E宽带应用型家庭网关牌照合作注册机制............................................................................ 附录F家庭网关命名规则 ..............................................................................................................。

imap rfc标准

Internet Message Access Protocol (IMAP) is an email retrieval protocol. It stores email messages on a mail server and enables the recipient to view and manipulate them as though they were stored locally on their device. IMAP was developed in the late 1980s and has since become one of the most widely used email retrieval protocols.The IMAP standard is defined in RFC 3501, which was published in 2003. This document provides a detailed description of the protocol's functionality, including its data formats, commands, and responses. The standard specifies how IMAP clients and servers should communicate with each other to enable the retrieval and manipulation of email messages.One of the key features of IMAP is its support for multiple clients accessing the same mailbox simultaneously. This is achieved through the use of a "shared" storage model, where all clients see the same set of messages and folders stored on the server. This allows users to access their email from different devices without having to worry about synchronizing their messages manually.Another important aspect of IMAP is its support for message organization and management. Clients can create, delete, and rename folders, as well as move messages between folders. They can also search for specific messages based on various criteria, such as sender, subject, or date.IMAP also provides a range of features for managing individual messages. Clients can mark messages as read or unread, flag them for follow-up, and even move them to a specific folder. They can also reply to messages, forward them to others, and generate replies or forwards with attachments.Overall, the IMAP standard provides a powerful and flexible framework for managing email messages. Its support for shared storage, message organization, and advanced message management features make it a popular choice for both personal and business email users.。

中移动家庭网关终端技术规范v3.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.0.0╳╳╳╳-╳╳-╳╳发布╳╳╳╳-╳╳-╳╳实施目录1. 范围 (1)2. 规范性引用文件 (1)3. 术语、定义和缩略语 (5)4. 设备总体定义 (9)4.1.设备在网络中的位置 (9)4.2.接口定义 (10)4.3.设备类型 (10)5. 接入型家庭网关 (11)5.1.接口要求 (11)5.1.1. 网络侧接口 (11)5.1.1.1. 网络侧接口描述 (11)5.1.1.2. 网络侧以太网接口要求 (12)5.1.1.3. PON接口要求 (12)5.1.1.4. TD-SCDMA接口要求 (12)5.1.1.5. TD-LTE接口要求 (12)5.1.2. 用户侧接口 (12)5.1.2.1. 用户侧以太网接口要求 (12)5.1.2.2. WLAN接口 (12)5.1.2.3. USB接口（可选） (12)5.2.功能要求 (13)5.2.1. 数据通信要求 (13)5.2.1.1. IP协议要求 (13)5.2.1.2. 数据转发功能要求 (13)5.2.1.3. DNS功能要求 (14)5.2.1.4. IPv4地址管理及拨号管理功能要求 (14)5.2.1.5. IPv6地址管理及拨号管理功能要求 (16)5.2.1.6. IPv4 NAT要求 (16)5.2.1.7. ALG要求 (17)5.2.1.8. 组播要求 (17)5.2.1.9. 其他功能要求 (17)5.2.2. 安全要求 (17)5.2.2.1. 防火墙 (17)5.2.2.2. 登陆WEB页面的安全要求 (17)5.2.2.3. 设备安全性 (18)5.2.3. QoS 要求 (18)5.2.4. VLAN功能要求 (19)5.2.5. USB扩展及管理（可选） (19)5.2.6. 设备发现要求 (19)5.2.6.1. UPnP (19)5.2.6.2. DLNA（可选） (19)5.2.7.1. 支持WLAN的开启和禁用 (20)5.2.7.2. 基本要求 (20)5.2.7.3. 多SSID要求 (20)5.2.7.4. WLAN安全要求 (20)5.2.7.5. WLAN QoS要求 (21)5.2.7.6. WPS要求 (21)5.2.8. 基本应用要求 (22)5.2.8.1. WLAN共享 (22)5.2.8.2. 家庭存储（可选） (23)5.3.性能要求 (23)5.3.1. 路由转发性能要求 (23)5.3.1.1. 吞吐量 (23)5.3.1.2. 地址学习 (23)5.3.1.3. 缓存大小 (23)5.3.1.4. 连接数量要求 (24)5.3.2. WLAN无线性能要求 (24)5.3.2.1. WLAN吞吐量性能要求 (24)5.3.2.2. WLAN覆盖性能要求 (24)5.3.2.3. WLAN接收灵敏度要求 (24)5.4.管理和维护要求 (24)5.4.1. 本地管理和配置要求 (24)5.4.1.1. 本地管理基本要求 (24)5.4.1.2. 用户分级管理 (25)5.4.1.3. 系统信息管理 (25)5.4.1.4. 基本配置 (25)5.4.1.5. 高级配置 (26)5.4.1.6. 设备管理 (27)5.4.1.7. 网络诊断 (27)5.4.1.8. 设备认证注册功能 (27)5.4.2. 远程管理要求 (29)5.4.2.1. 远程管理基本要求 (30)5.4.2.2. 远程参数配置和性能监测 (30)5.4.2.3. 远程故障诊断功能 (30)5.4.2.4. 设备告警功能 (30)5.4.2.5. 远程链路维持功能 (31)5.4.2.6. 软件远程管理 (31)5.4.2.7. 业务部署和控制 (31)5.4.2.8. PON上行家庭网关远程管理实现方式 (31)5.4.3. 日志功能要求 (32)5.5.预配置要求 (33)5.5.1. 预配置要求 (33)5.6.硬件要求 (34)5.6.1. 基本要求 (34)5.6.3. 硬件基本框图示例 (34)5.7.软件要求 (34)5.7.1. 基本要求 (34)5.7.2. 软件基本架构 (35)5.7.3. 软件接口要求 (35)5.7.4. 用户登录要求 (36)5.7.5. 系统升级要求 (36)5.8.配置界面要求 (36)5.8.1. 配置界面要求 (36)5.8.2. 配置界面用户权限要求 (36)5.9.设备标识要求 (38)5.10.外观及附件要求 (39)5.10.1. 运营商Logo要求 (39)5.10.2. 设备标签要求 (39)5.10.3. 网关指示灯要求 (40)5.10.4. 开关与按键要求 (41)5.10.5. 设备面板标识要求 (41)5.10.6. 设备接口要求 (41)5.10.7. 附件要求 (41)5.11.运行环境要求 (42)5.11.1. 供电要求 (42)5.11.2. 环境要求 (42)5.11.3. 抗电磁干扰能力 (42)5.11.4. 设备本身产生的电磁干扰要求 (42)5.11.5. 过压过流保护 (42)5.12.认证要求 (43)6. 接入型家庭网关支持物联网功能 (43)6.1.接入型家庭网关支持宜居通的功能要求（内置433M模块） (43)6.1.1. 433M模块要求 (43)6.1.2. 外围设备要求 (43)6.1.3. 业务功能描述 (43)6.1.3.1. 安防功能要求 (44)6.1.3.2. 家电控制功能 (44)6.1.4. 接入型家庭网关配置界面要求 (45)6.1.4.1.配置界面要求 (45)6.1.4.2. 配置界面用户权限要求 (46)6.2.接入型家庭网关支持基于低功耗W I F I的物联网功能要求 (48)6.2.1. 设备接入功能要求 (48)6.2.1.1. WiFi接入 (48)6.2.1.1.1. 接入型家庭网关要求 (48)6.2.1.1.2. 外设要求 (49)6.2.1.2. DHCP流程要求 (49)7. 宽带应用型家庭网关 (49)7.1.类型描述 (49)7.2.分体机接入设备要求 (49)7.3.分体机应用设备（机顶盒）要求 (50)7.3.1. 硬件要求 (50)7.3.1.1. 硬件、接口及按键要求 (50)7.3.1.2. 遥控器要求及参考设计 (53)7.3.1.3. 电源要求 (53)7.3.1.4. 配件要求 (53)7.3.1.5. 设备标识要求 (53)7.3.2. 网络侧接口要求 (54)7.3.3. 业务功能要求 (54)7.3.3.1. 互联网电视应用 (54)7.3.3.2. 多屏互动功能 (54)7.3.3.2.1. 概述 (54)7.3.3.2.2. 镜像功能 (54)7.3.3.2.3. 分享功能 (55)7.3.3.3. 家庭高清视频通话（可选） (55)7.3.3.4. 家庭卡拉OK功能（可选） (56)7.3.3.5. 语音交互功能 (56)7.3.4. 软件要求 (56)7.3.4.1. 操作系统要求 (56)7.3.4.2. 软件协议要求 (57)7.3.4.3. 编码及解码能力要求 (57)7.3.4.3.1. 编解码能力要求 (57)7.3.4.3.2. 音视频播放质量要求 (58)7.3.4.4. 屏幕管理要求 (58)7.3.4.5. 防刷机要求 (58)7.3.5. 管理要求 (59)7.3.5.1. 操作管理 (59)7.3.5.2. 软件管理 (60)7.3.5.3. 文件管理 (60)7.3.5.4. 配置管理 (60)7.3.6. 其他要求 (61)7.3.6.1. 供电要求 (61)7.3.6.2. 环境要求 (61)7.3.6.3. 噪声要求 (62)7.4.一体机设备要求 (62)7.4.1. 网络侧接口要求 (62)7.4.2. 网络接入功能要求 (62)7.4.3. 业务功能要求 (62)7.4.4. 软件要求 (62)7.4.5. 管理要求 (62)7.4.6. 硬件要求 (62)7.4.7. 其他要求 (62)7.4.7.1. 供电要求 (62)7.4.7.2. 环境要求 (63)7.4.7.3. 噪声要求 (63)8. 编制历史 (63)附录A省公司代码 (64)附录B设备故障消息（标准性附录） (65)B.1 告警编号规则 (65)B.2 设备告警信息列表 (66)附录C WIMO协议说明 (67)C.1设备类型和功能流程 (67)C.2网络连接 (68)C.3设备连接 (69)C.4媒体格式要求 (70)C.4.1视频编解码流程 (70)C.4.2 M-JPEG视频编解码方案 (70)C.4.3 H.264视频编解码方案 (70)C.4.4 音频编解码流程 (70)附录D手机遥控接口说明 .............................................................................. 错误!未定义书签。

IETF会议介绍

Progress since IETF 74 plenary discussion draft-dawkins-nomcom-dont-wait:

27 May 2009 (-03) IETF Last Call started 24 June 2009 (-03) IESG Evaluation started 6 July 2009 (-04) Update I-D to specify when the IETF Secretariat issues the announcement and solicitation, and specify that the IETF Secretariat collects the responses and delivers them to the incoming NomCom chair 7 July 2009 (-04) IESG Approval
Title Abstract Status of This Memo IESG Note (if necessary) Copyright Notice Introduction
6
IANA Activity since IETF 74
(actually Mar 2009-Jun 2009)

Processed 1714 IETF-related requests, including:

8 New WG, 6 Closed WGs

Approximately 112 WGs currently chartered

517 New I-Ds (125 were updated, 25 more than once)

RFC1636

7.2 建议性的中期作用 38
7.3 建议性的长期操作 38
1.简介
IAB(internet Architecture Board) 保存了长期以来临时（occasional）活动中心有计划的对Internet网络的一些观点和策略，为Internet体系结构的未来发展提供一些建议。在IESG(internet Engineering Steering Group) 和地区董事会的领导下，IAB的长期目的就是对IETF(internet Engineering Steering Group)工作组正在进行的努力做一个有益的补充。
在摘要中，该活动中心的目的有如下两个方面：
（1）. 对安全和Internet体系结构中其它方面的互联技术的研究
(2). 对Internet安全方面的发展趋势做出一些建议，这些目的在IAB中总结为两个最重要的关于Internet 体系结构问题――缩放比例（Scaling ）和安全。前者导致了Ipng的积极讨论。这里有少量的关于安全方面的成果。
该活动中心在防火墙路由器的构建上花了大量的时间进行研究，主要在第三章进行描述。
C 安全的QOS
Intenet 被扩展到可以提供服务质量的功能，在该中心这个主题被称作为“实时服务”（real time service）。这些扩展为网络结构提出了一套新的安全策略，来确保用户不可访问他们未经授权使用的资源，同时预防资源被盗用和防止由于那些未经授权用户的访问所导致的服务器的拒绝访问（也就是防止通信的阻塞）。被保护的资源包括联机共享（link shares）,服务类或队列（ service classes or queues）,多点传送树（ multicast trees）等等，这些资源被用于网络的虚拟通道（virtual channels），每一个虚拟通道都被一个详细的传输包的子集（subset）或类（class）使用。

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在互联网技术领域起着重要的作用，它们记录了互联网协议的发展历程和指导原则。

rfc3326(The Reason Header Field for the Session Initiation Protocol (SIP))

the final error response in a provisional response. The Reason header
field is a candidate to be used for such encapsulation.
Schulzrinne, et. al. Standards Track [Page 2]
RFC 3326 The Reason Header Field for SIP December 2002
Initially, the Reason header field defined here appears to be most
useful for BYE and CANCEL requests, but it can appear in any request
6. Acknowledgments ............................................ 7
7. Authors' Addresses ......................................... 7
8. Normative References ....................................... 7
December 2002
The Reason Header Field for the Session Initiation Protocol (SIP)
Status of this Memo
3.4. ISUP interworking .......................................... 5
4. IANA Considerations ........................................ 6

rfc4716.The Secure Shell (SSH) Public Key File Format

Network Working Group J. Galbraith Request for Comments: 4716 VanDyke Software Category: Informational R. Thayer Canola & Jones November 2006 The Secure Shell (SSH) Public Key File FormatStatus of This MemoThis memo provides information for the Internet community. It doesnot specify an Internet standard of any kind. Distribution of thismemo is unlimited.Copyright NoticeCopyright (C) The IETF Trust (2006).AbstractThis document formally documents an existing public key file formatin use for exchanging public keys between different Secure Shell(SSH) implementations.In addition, this document defines a standard textual representation for SSH public key fingerprints.Table of Contents1. Introduction (2)2. Conventions Used in This Document (2)3. Key File Format (2)3.1. Line Termination Characters (2)3.2. Begin and End Markers (3)3.3. Key File Header (3)3.3.1. Subject Header (3)3.3.2. Comment Header (4)3.3.3. Private Use Headers (4)3.4. Public Key File Body (4)3.5. Differences with RFC 1421 PEM Formats (4)3.6. Examples (5)4. Public Key Fingerprints (6)5. IANA Considerations (6)6. Security Considerations (7)7. References (8)7.1. Normative References (8)7.2. Informative References (8)Galbraith & Thayer Informational [Page 1]1. IntroductionThe SSH protocol supports the use of public/private key pairs inorder to perform authentication based on public key cryptography.However, in order to use public key authentication in the SSHprotocol, public keys must first be exchanged between client andserver.This document formally describes an existing public key file formatthat can be used with any of the common existing file transfermechanisms in order to exchange public keys.The SSH protocol also uses public/private key pairs to authenticatethe server. In this scenario, it is important to verify that thepublic key provided by the server is indeed the server’s public key. This document describes a mechanism for creating a short text string that uniquely represents a particular public key, calledfingerprinting.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. Key File FormatIn order to implement public key authentication, SSH implementations must share public key files between the client and the server inorder to interoperate.A key file is a text file, containing a sequence of lines. Each line in the file MUST NOT be longer than 72 8-bit bytes excluding linetermination characters.3.1. Line Termination CharactersImplementations SHOULD generate public key files using their system’s local text file representation.In the event that public key files are not transferred as text files, implementations SHOULD be prepared to read files using any of thecommon line termination sequence, <CR>, <LF>, or <CR><LF>.Galbraith & Thayer Informational [Page 2]3.2. Begin and End MarkersThe first line of a conforming key file MUST be a begin marker, which is the literal text:---- BEGIN SSH2 PUBLIC KEY ----The last line of a conforming key file MUST be an end marker, whichis the literal text:---- END SSH2 PUBLIC KEY ----3.3. Key File HeaderThe key file header section consists of multiple RFC822-style header fields. Each field is a line of the following format:Header-tag ’:’ ’ ’ Header-valueThe Header-tag MUST NOT be more than 64 8-bit bytes and is case-insensitive. The Header-value MUST NOT be more than 1024 8-bitbytes. Each line in the header MUST NOT be more than 72 8-bit bytes.A line is continued if the last character in the line is a ’\’. Ifthe last character of a line is a ’\’, then the logical contents ofthe line are formed by removing the ’\’ and the line terminationcharacters, and appending the contents of the next line.The Header-tag MUST be encoded in US-ASCII. The Header-value MUST be encoded in UTF-8 [RFC3629].A line that is not a continuation line that has no ’:’ in it is thefirst line of the base64-encoded body. (See Section 3.4.)The space of header-tags is managed as described in Section 5.Compliant implementations MUST ignore headers with unrecognizedheader-tags. Implementations SHOULD preserve such unrecognizedheaders when manipulating the key file.3.3.1. Subject HeaderThis field is used to store the login-name that the key was generated under. For example:Subject: userGalbraith & Thayer Informational [Page 3]3.3.2. Comment HeaderThe comment header contains a user-specified comment. The commentSHOULD be displayed when using the key.It is suggested that this field default to user@hostname for the user and machine used to generate the key. For example:Comment: user@Currently, common practice is to quote the Header-value of theComment by prefixing and suffixing it with ’"’ characters, and someexisting implementations fail if these quotation marks are omitted.Compliant implementations MUST function correctly if the quotationmarks are omitted.Implementations MAY include the quotation marks. If the first andlast characters of the Header-value are matching quotation marks,implementations SHOULD remove them before using the value.3.3.3. Private Use HeadersHeaders with header-tags beginning with "x-" are reserved for private use.3.4. Public Key File BodyThe body of a public key file is the base64 encoded ([RFC2045])public key data as specified by [RFC4253], Section 6.6:string certificate or public key format identifierbyte[n] key/certificate dataAs with all other lines, each line in the body MUST NOT be longerthan 72 8-bit bytes excluding line termination characters.3.5. Differences with RFC 1421 PEM FormatsImplementers should take care to notice that while the format issuperficially similar to those specified by PEM [RFC1421] and OpenPGP [RFC2440], it is not identical; most notably:o The other specifications use different BEGIN/END delimiters (five dashes, no space rather than four dashes and a space).o There is no blank line before the start of the base64-encodedcontents.Galbraith & Thayer Informational [Page 4]o There is no Cyclic Redundancy Check (CRC) at the end of thebase64-encoded block.o Header continuation uses a backslash at the end of the continuedline rather than whitespace at the start of the next line.3.6. ExamplesThe following are some examples of public key files that arecompliant (note that the examples all wrap before 72 bytes to meetIETF document requirements; however, they are still compliant.)---- BEGIN SSH2 PUBLIC KEY ----Comment: "1024-bit RSA, converted from OpenSSH by me@"x-command: /home/me/bin/lock-in-guest.shAAAAB3NzaC1yc2EAAAABIwAAAIEA1on8gxCGJJWSRT4uOrR13mUaUk0hRf4RzxSZ1zRb YYFw8pfGesIFoEuVth4HKyF8k1y4mRUnYHP1XNMNMJl1JcEArC2asV8sHf6zSPVffozZ 5TT4SfsUu/iKy9lUcCfXzwre4WWZSXXcPff+EHtWshahu3WzBdnGxm5Xoi89zcE=---- END SSH2 PUBLIC KEY -------- BEGIN SSH2 PUBLIC KEY ----Comment: This is my public key for use on \servers which I don’t like.AAAAB3NzaC1kc3MAAACBAPY8ZOHY2yFSJA6XYC9HRwNHxaehvx5wOJ0rzZdzoSOXxbET W6ToHv8D1UJ/z+zHo9Fiko5XybZnDIaBDHtblQ+Yp7StxyltHnXF1YLfKD1G4T6JYrdH YI14Om1eg9e4NnCRleaqoZPF3UGfZia6bXrGTQf3gJq2e7Yisk/gF+1VAAAAFQDb8D5c vwHWTZDPfX0D2s9Rd7NBvQAAAIEAlN92+Bb7D4KLYk3IwRbXblwXdkPggA4pfdtW9vGf J0/RHd+NjB4eo1D+0dix6tXwYGN7PKS5R/FXPNwxHPapcj9uL1Jn2AWQ2dsknf+i/FAA vioUPkmdMc0zuWoSOEsSNhVDtX3WdvVcGcBq9cetzrtOKWOocJmJ80qadxTRHtUAAACB AN7CY+KKv1gHpRzFwdQm7HK9bb1LAo2KwaoXnadFgeptNBQeSXG1vO+JsvphVMBJc9HS n24VYtYtsMu74qXviYjziVucWKjjKEb11juqnF0GDlB3VVmxHLmxnAz643WK42Z7dLM5 sY29ouezv4Xz2PuMch5VGPP+CDqzCM4loWgV---- END SSH2 PUBLIC KEY -------- BEGIN SSH2 PUBLIC KEY ----Comment: DSA Public Key for use with MyIspAAAAB3NzaC1kc3MAAACBAPY8ZOHY2yFSJA6XYC9HRwNHxaehvx5wOJ0rzZdzoSOXxbET W6ToHv8D1UJ/z+zHo9Fiko5XybZnDIaBDHtblQ+Yp7StxyltHnXF1YLfKD1G4T6JYrdH YI14Om1eg9e4NnCRleaqoZPF3UGfZia6bXrGTQf3gJq2e7Yisk/gF+1VAAAAFQDb8D5c vwHWTZDPfX0D2s9Rd7NBvQAAAIEAlN92+Bb7D4KLYk3IwRbXblwXdkPggA4pfdtW9vGf J0/RHd+NjB4eo1D+0dix6tXwYGN7PKS5R/FXPNwxHPapcj9uL1Jn2AWQ2dsknf+i/FAA vioUPkmdMc0zuWoSOEsSNhVDtX3WdvVcGcBq9cetzrtOKWOocJmJ80qadxTRHtUAAACB AN7CY+KKv1gHpRzFwdQm7HK9bb1LAo2KwaoXnadFgeptNBQeSXG1vO+JsvphVMBJc9HS n24VYtYtsMu74qXviYjziVucWKjjKEb11juqnF0GDlB3VVmxHLmxnAz643WK42Z7dLM5 sY29ouezv4Xz2PuMch5VGPP+CDqzCM4loWgV---- END SSH2 PUBLIC KEY ----Galbraith & Thayer Informational [Page 5]---- BEGIN SSH2 PUBLIC KEY ----Subject: meComment: 1024-bit rsa, created by me@ Mon Jan 15 \08:31:24 2001AAAAB3NzaC1yc2EAAAABJQAAAIEAiPWx6WM4lhHNedGfBpPJNPpZ7yKu+dnn1SJejgt4 596k6YjzGGphH2TUxwKzxcKDKKezwkpfnxPkSMkuEspGRt/aZZ9wa++Oi7Qkr8prgHc4 soW6NUlfDzpvZK2H5E7eQaSeP3SAwGmQKUFHCddNaP0L+hM7zhFNzjFvpaMgJw0=---- END SSH2 PUBLIC KEY ----4. Public Key FingerprintsThe security of the SSH protocols relies on the verification ofpublic host keys. Since public keys tend to be very large, it isdifficult for a human to verify an entire host key. Even with aPublic Key Infrastructure (PKI) in place, it is useful to have astandard for exchanging short fingerprints of public keys.This section formally describes the method of generating public keyfingerprints that is in common use in the SSH community.The fingerprint of a public key consists of the output of the MD5message-digest algorithm [RFC1321]. The input to the algorithm isthe public key data as specified by [RFC4253]. (This is the samedata that is base64 encoded to form the body of the public key file.)The output of the algorithm is presented to the user as a sequence of 16 octets printed as hexadecimal with lowercase letters and separated by colons.For example: "c1:b1:30:29:d7:b8:de:6c:97:77:10:d7:46:41:63:87"5. IANA ConsiderationsSection 3.3 defines a new namespace of "Header-tags". These areUS-ASCII strings of maximum length 64 characters and arecase-insensitive.IANA has created and maintains a registry of these header-tags. The registry maps each header-tag to a reference defining the header.The initial contents of the registry are as follows:subject defined in Section 3.3.1comment defined in Section 3.3.2Header-tags beginning with "x-" are reserved for private use, asdefined in [RFC2434].Galbraith & Thayer Informational [Page 6]All other allocations are to be made by IETF consensus, as defined in [RFC2434].6. Security ConsiderationsThe file format described by this document provides no mechanism toverify the integrity or otherwise detect tampering with the datastored in such files. Given the potential of adversarial tamperingwith this data, system-specific measures (e.g., Access Control Lists, UNIX permissions, other Discretionary and/or Mandatory AccessControls) SHOULD be used to protect these files. Also, if thecontents of these files are transferred it SHOULD be done over atrusted channel.The header data allowed by this file format could contain anunlimited range of information. While in many environments theinformation conveyed by this header data may be considered innocuous public information, it may constitute a channel through whichinformation about a user, a key, or its use may be disclosedintentionally or otherwise (e.g., "Comment: Mary E. Jones, 123 MainSt, Home Phone:..."). The presence and use of this header dataSHOULD be reviewed by sites that deploy this file format.The public key fingerprint method presented here relies on the MD5one-way hash function, which is known to have certain weaknessesregarding its collision resistance; however, the particular use made of MD5 here depends solely on its 2nd-preimage resistance, not on its collision resistance.MD5 is used here for historical reasons.Galbraith & Thayer Informational [Page 7]7. References7.1. Normative References[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April 1992.[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet MailExtensions (MIME) Part One: Format of Internet MessageBodies", RFC 2045, November 1996.[RFC2119] Bradner, S., "Key words for use in RFCs to IndicateRequirement Levels", BCP 14, RFC 2119, March 1997.[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO10646", STD 63, RFC 3629, November 2003.[RFC4253] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)Transport Layer Protocol", RFC 4253, January 2006.[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing anIANA Considerations Section in RFCs", BCP 26, RFC 2434,October 1998.7.2. Informative References[RFC1421] Linn, J., "Privacy Enhancement for Internet ElectronicMail: Part I: Message Encryption and AuthenticationProcedures", RFC 1421, February 1993.[RFC2440] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer,"OpenPGP Message Format", RFC 2440, November 1998.Galbraith & Thayer Informational [Page 8]Authors’ AddressesJoseph GalbraithVanDyke Software4848 Tramway Ridge BlvdSuite 101Albuquerque, NM 87111USPhone: +1 505 332 5700EMail: galb@Rodney ThayerCanola & Jones650 Castro Street Suite 120-205Mountain View CA 94041USPhone: +1 650 704 8389EMail: rodney@Galbraith & Thayer Informational [Page 9]Full Copyright StatementCopyright (C) The IETF Trust (2006).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 THATTHE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE.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@.AcknowledgementFunding for the RFC Editor function is currently provided by theInternet Society.Galbraith & Thayer Informational [Page 10]。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

Network Working Group IAB Advisory Committee Request for Comments: 3716 IETF Category: Informational March 2004 The IETF in the Large: Administration and ExecutionStatus of this MemoThis memo provides information for the Internet community. It doesnot specify an Internet standard of any kind. Distribution of thismemo is unlimited.Copyright NoticeCopyright (C) The Internet Society (2004). All Rights Reserved. AbstractIn the fall of 2003, the IETF Chair and the IAB Chair formed an IABAdvisory Committee (AdvComm), with a mandate to review the existingIETF administrative structure and relationships (RFC Editor, IETFSecretariat, IANA) and to propose changes to the IETF managementprocess or structure to improve the overall functioning of the IETF. The AdvComm mandate did not include the standards process itself.This memo documents the AdvComm’s findings and proposals.Table of Contents1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 21.1. Overview of the AdvComm Work Process and Output. . . . 31.2. Scope. . . . . . . . . . . . . . . . . . . . . . . . . 31.3. Next Steps . . . . . . . . . . . . . . . . . . . . . . 42. Observations . . . . . . . . . . . . . . . . . . . . . . . . 42.1. Current IETF Support Structure . . . . . . . . . . . . 42.1.1. What the Term IETF Includes in this Document . 42.1.2. Functions. . . . . . . . . . . . . . . . . . . 42.1.3. Support. . . . . . . . . . . . . . . . . . . . 62.2. Observed Stress Points . . . . . . . . . . . . . . . . 82.2.1. Stress Points Observed by IETF Leadership. . . 82.2.2. Stress Points Observed by OrganizationsSupporting the IETF. . . . . . . . . . . . . . 102.3. A final Observation. . . . . . . . . . . . . . . . . . 103. Stand Facing the Future: Requirements for a SuccessfulIETF Administration. . . . . . . . . . . . . . . . . . . . . 103.1. Resource Management. . . . . . . . . . . . . . . . . . 103.1.1. Uniform Budgetary Responsibility . . . . . . . 10 IAB Advisory Committee Informational [Page 1]3.1.2. Revenue Source Equivalence . . . . . . . . . . 113.1.3. Clarity in Relationship with SupportingOrganizations. . . . . . . . . . . . . . . . . 113.1.4. Flexibility in Service Provisioning. . . . . . 113.1.5. Administrative Efficiency. . . . . . . . . . . 113.2. Stewardship. . . . . . . . . . . . . . . . . . . . . . 123.2.1. Accountability for Change. . . . . . . . . . . 123.2.2. Persistence and Accessibility of Records . . . 123.3. Working Environment. . . . . . . . . . . . . . . . . . 123.3.1. Service Automation . . . . . . . . . . . . . . 123.3.2. Tools. . . . . . . . . . . . . . . . . . . . . 134. Advisory Committee Advice . . . . . . . . . . . . . . . . . 134.1. Proposed: (Single) Formalized IETF OrganizationalEntity . . . . . . . . . . . . . . . . . . . . . . . . 134.1.1. Comments on the Necessity of thisFormalization. . . . . . . . . . . . . . . . . 144.2. Possible Structures. . . . . . . . . . . . . . . . . . 144.2.1. ISOC . . . . . . . . . . . . . . . . . . . . . 154.2.2. ISOC Subsidiary. . . . . . . . . . . . . . . . 154.2.3. Completely Autonomous Organizational Entity. . 164.3. Who Can Decide . . . . . . . . . . . . . . . . . . . . 175. Security Considerations. . . . . . . . . . . . . . . . . . . 176. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 177. Informative References . . . . . . . . . . . . . . . . . . . 18A. IAB Advisory Committee Charter . . . . . . . . . . . . . . . 19B. Input from the current IETF and IAB Chairs . . . . . . . . . 20C. Consultation with ISI: RFC Editor . . . . . . . . . . . . . 21D. Consultation with Foretec/CNRI: Secretariat and MeetingPlanning . . . . . . . . . . . . . . . . . . . . . . . . . . 32E. Consultation with ICANN: IANA Protocol ParameterAssignment . . . . . . . . . . . . . . . . . . . . . . . . . 35Author’s Address . . . . . . . . . . . . . . . . . . . . . . 39Full Copyright Statement . . . . . . . . . . . . . . . . . . 40 1. IntroductionIn the fall of 2003, the IETF Chair and the IAB Chair formed an IABAdvisory Committee (AdvComm), with a mandate to review the existingIETF administrative structure and relationships (RFC Editor, IETFSecretariat, IANA) and to propose changes to the IETF managementprocess or structure to improve the overall functioning of the IETF. This purpose was defined in the IAB Advisory Committee (AdvComm)charter, copied in Appendix A. The AdvComm mandate did not includethe standards process itself.IAB Advisory Committee Informational [Page 2]The tangible output of this committee is a set of observations andrecommendations for the IETF’s executive structure - how the IETFmight be organizationally (re)structured so that it can effectivelyand efficiently carry out its administrative activities. As anecessary preamble to that, a description of the current issues andfuture requirements is presented. The output does not represent any decision-making or implementation -- see Section 1.3 for a discussion of follow-on steps.1.1. Overview of the AdvComm Work Process and OutputThe AdvComm was formed in September 2003, and carried out its workover the course of the following 2 months, prior to the IETF58 inNovember of 2003.The AdvComm’s membership included many of the individuals who are, or have been, volunteered to manage the IETF’s inter-organizationadministrative relationships in recent years. The first phase of the committee’s work, therefore, included sharing and discussing the body of tacit knowledge about those relationships. This included theinput from the current IETF and IAB Chairs in Appendix B, and yielded the IETF organizational structure information in Section 2.1.The committee also sought input from the other end of the keyexisting administrative relationships (RFC Editor, Secretariat, andIANA). The output of those efforts is included in Appendix C,Appendix D, and Appendix E, and these were also used as the basis for the observations in Section 2.From these inputs, the committee drew together a list of requirements for successful future IETF administration, documented in Section 3.Finally, the committee put together some advice for how the IETFmight consider reorganizing its administrative structure to meetthose requirements moving forward -- Section 4.1.2. ScopeThe AdvComm endeavored to stay focused on the IETF executivestructure -- the collection of organizations that work together tobring the IETF’s work to reality. However, by virtue of the veryfact that those relationships exist to get the work done, it wasimportant to bear in mind the work being done in the IETF PROBLEMworking group and IESG proposals for change, even as the committeeendeavored not to infringe on the scope of those efforts. Theobjective is that these observations and proposals should be relevant for today’s IETF and any near-term evolutions that are deemedappropriate.IAB Advisory Committee Informational [Page 3]1.3. Next StepsThis documents the state of the AdvComm’s thinking at the end of atwo month process, and brings the currently-chartered work of theAdvComm to a close.Next steps include review of this material by the community, andspecific proposals for action that will be put forward by the IAB and IETF Chairs.2. Observations2.1. Current IETF Support Structure2.1.1. What the Term IETF Includes in this DocumentRFC 3233 ([1]) provides a definition of the IETF, in terms of itswork and its participation.This document discusses the collection of organizations that worktogether to support the effort described in RFC 3233. In thisdocument, the term "IETF" explicitly includes the IESG, WGs, IAB,IRTF, and RGs. This inclusive sense accords with considerable common usage of the term "IETF". Formally, the IAB and IRTF are charteredindependently of the IETF. However, rather than coming up with a new term to encompass "the IETF and all its friends", the common usage is followed here.2.1.2. FunctionsThe work of the IETF is supported by a specific set of functions. It is useful to distinguish between the functions and the organizations which provide those services, as outlined in the table below. Insome cases a single organization provides multiple services, but the functions are logically distinct.IAB Advisory Committee Informational [Page 4]Function Known as Organization(within the IETF)--------- ---------------- ------------IESG Support Secretariat Foretec/CNRIIAB Support ISOC/Secretariat ISOC, Foretec/CNRI WG Support Secretariat Foretec/CNRICommunity Support Secretariat Foretec/CNRIIETF Meetings Secretariat Foretec/CNRIRFC Publication RFC Editor USC/ISIStandards Status Record RFC Editor USC/ISIParameter Reg. IANA ICANNLegal, insurance, etc. (largely invisible) Provided by ISOCTable 1. IETF functions, labels and organizationsIn more detail, the functions can be broken down as follows:IESG SupportTelechatsCommunicationsIETF document trackingWorking document management (mailing list, website, repository)IAB supportTelechatsCommunicationsWorking document management (mailing list, website, repository)WG supportChartersMilestone trackingWorkspace (website, mailing list)Working document archive (mailing list archives, documentrepository)Community SupportWebsiteIETF mailing listAnnouncementsI-D repositoryIAB Advisory Committee Informational [Page 5]RFC PublicationWebsiteRFC editorialDocument publicationRFC repository managementOfficial standards status recordIETF MeetingsPlanningMeeting ProceedingsProtocol parameter registrationCreation of registriesAssignment of protocol parametersManagement of accessible registry repositoryLegal, insurance, etc.Legal supportLiability insurance for IAB, IESG, WG chairs, etc.Miscellaneous2.1.3. SupportA presentation of the scope and depth of support that created theIETF and has allowed it to continue to contribute would require adiscussion of history that is rich, vibrant, and completely beyondthe scope of this document. However, a very brief introduction tosome of the current pillars is needed to understand where the IETF is today.ISOC: Since 1992, ISOC has been the organizational home of theIETF. This activity is part of its more general mission ofserving as the international organization for global coordination and cooperation on the Internet, promoting and maintaining a broad spectrum of activities focused on the Internet’s development,availability, and associated technologies.Foretec/CNRI: The Corporation for National Research Initiatives(CNRI) was founded in 1986, and since 1987, CNRI has served thecommunity by providing IETF Secretariat services. Until the early 1990s, CNRI provided legal assistance to the IETF and the IETFSecretariat. After ISOC was founded, ISOC assumed overall legalresponsibility for the substantive workings of the IETF including the efforts of the IETF chair, the IESG, the IAB, the areaIAB Advisory Committee Informational [Page 6]directors and the working group chairs. CNRI assumed operational responsibility for the substantive workings of the IETFSecretariat. In 1998, in order to decrease overhead costs on the activities, the Secretariat was reorganized placing Secretariatemployees including the IETF Executive Director in a CNRI for-profit subsidiary (Foretec Seminars, Inc.). Foretec was foundedin 1997, in anticipation of the Secretariat becoming self-supporting. CNRI and its subsidiary have continued to improve the operation of the Secretariat, as appropriate, and maintain atrained staff.USC/ISI: The role of the RFC Editor, and USC/ISI, is detailed in RFC 2555. The RFC document series is a set of technical andorganizational notes about the Internet (originally the ARPANET), beginning in 1969. For 30 years, the RFC Editor was Jon Postel, a research scientist and manager in the Networking Division of theUSC Information Sciences Institute (ISI), with the functiongradually evolving into a team headed by him. The RFC Editoractivity is currently organized as a project within ISI, using the ISI infrastructure, and supported by a contract with ISOC. TheRFC Editor is the publisher of RFCs and is responsible for thefinal editorial review of the documents, as well as themaintenance of the online repository and index of those documents. ICANN: The Internet Corporation for Assigned Names and Numbers(ICANN) is the non-profit corporation that was formed in 1998 toassume responsibility for the IP address space allocation,protocol parameter assignment, domain name system management, and root server system management functions previously performed under U.S. Government contract by IANA (at ISI) and other entities.The support picture (who does what) can be described as follows:Secretariat at Foretec/CNRIIESG SupportIAB Support (working document management)WG SupportCommunity SupportIETF meetingsRFC Editor at USC/ISI[Supported by ISOC, based on a contract between USC/ISI and ISOC] RFC publication Maintenance of standards status recordIAB Advisory Committee Informational [Page 7]IANA/ICANN[Relationship defined by Memorandum of Understanding: RFC 2860]Protocol parameter registryISOCIAB Support (Telechats)Funds RFC EditorMisc IAB/IESG expensesProvides insurance for IAB, IESG, WG chairs, etc.The available resources to support these activities are:Meeting fees -- through ForetecISOC members’ contributions for standardsICANN for IANAVolunteers/their employers (where applicable):IETF participantsWG chairsDocument editorsIETF NomComIESGIABIAB ExecDir2.2. Observed Stress PointsThe AdvComm noted several properties of the current IETForganizational environment that cause stress in the system. Thesehave been noted both from the point of view of the IETF leadership as well as that of organizations supporting the IETF.2.2.1. Stress Points Observed by IETF LeadershipThe current IETF funding and operational structure is dependent onIETF meeting attendance. Therefore, the most obvious stressor thathas emerged within the last two years is the decline in thatattendance. This trend, which has continued unabated, has resultedin a decline in IETF revenue (detailed in the IETF chair presentation at IETF 56 [2]), even as the requirements of the IETF operation areremaining constant or increasing.IAB Advisory Committee Informational [Page 8]The result has been a budget deficit for operations which began in2002, and is forecasted to continue until at least 2004, even after a substantial increase in meeting fees. The continuing deficits havedepleted working capital, making the IETF less robust againstpotential future budgetary disappointments.The financial stress is real, but the IETF leadership has notedseveral other stressors that are impediments to finding andimplementing solutions to the fiscal issues. Some obvious solutions are not implementable in the current IETF structure.The rest of the stressors listed in this section should be understood as issues for which relief is necessary, particularly in the light of needing to properly address and implement solutions to the financial stress.The current documentation of IETF processes and structure is, inplaces, vague about the distribution of responsibility for management and oversight of the IETF administrative relationships. This makesit opaque to the IETF community, and sometimes leaves the leadership in a poor position to manage effectively.Additionally, the informality of the relationships with some of theorganizations that are carrying out key IETF functions compounds the problem of determining who has responsibility, and how IETF community consensus and desires are reflected in the activity.As a separate issue, important IETF institutional memory is recorded nowhere other than peoples’ minds in many cases -- which requiressignificant transmission of oral history for IETF leadershiptransition to be effective.Apart from the institutional memory, other important IETFinstitutional records are spread across various organizations, andsearching for the set of relevant documentation (especially when this is necessary long after the recording) can be challenging.Another stressor relates to the need to scale support processes interms of reducing latency for mechanical processes. That is, adecrease in the amount of manual labor required for the simpler tasks between the organizations, would make more resources available tofocus on the special cases. Lack of automation in the basic request services has been known to cause undue delay or failure in processing simple, routine tasks. However, automation also requires resourcesand significant management in order to make sure it fulfills thecommunity’s requirements.IAB Advisory Committee Informational [Page 9]2.2.2. Stress Points Observed by Organizations Supporting the IETFSupporting organizations report difficulties in determiningauthoritative channels for directions -- either too many inputs, orno clear authority for resolution of change requests.In the absence of written agreements, supporting organizations maynot be clear from whom to take direction. Even where agreementsexist, the authority to provide direction may not be clear. Thegenesis of both problems is that the IETF relies on external bodiesfor support, but does not have sufficiently clear externalrelationships to allow it to provide input as to its requirements or direction on what services it desires.2.3. A Final ObservationThis section attempts to capture a snapshot of the current state ofthe IETF organization, without undue fixation on the causes forarriving at the current state. However, it seems clear from theobservations that the current state does not provide an adequatestructure from which to reach into the future: some changes areneeded within the IETF administrative and executive structure.3. Stand Facing the Future: Requirements for a Successful IETFAdministrationThis section follows the set of observations with a set ofrequirements for a properly-functioning IETF administrativestructure. These requirements are offered as the AdvComm’sdescription of what the IETF needs, without addressing immediatelythe degree to which they are available with the current environment. That is, these are "requirements", not "requirements for change".3.1. Resource Management3.1.1. Uniform Budgetary ResponsibilityThe IETF has operated in times of financial wealth and times ofeconomic cutbacks in the industry. It is reasonable to expect thatthe future holds similarly variable trends. Therefore, it isimportant that the IETF organization has the ability to make thedecisions to match its needs at a given point in time, i.e.,budgetary autonomy. At this particular moment, there are hardchoices to make, and the AdvComm believes that it is the IETFleadership, with the advice and consent of the IETF community, thatneeds to make them.IAB Advisory Committee Informational [Page 10]3.1.2. Revenue Source EquivalenceThe IETF is currently supported by money from multiple sources,including meeting fees, donations from interested corporate and non- corporate entities, and donations in kind of equipment or manpower.The IETF needs to be able to consider all sources of income, and all expenses involved in running the IETF, as pieces of one budget, to be free to adjust all items on the occasions when the income from thedifferent sources varies, and to allocate funds as reasonablyrequired.The usual caveats apply: that donations not threaten theindependence of the IETF, and that donations are easier when they are tax deductible.3.1.3. Clarity in Relationship with Supporting OrganizationsWhile the IETF needs to be able to manage its revenue streams against its expense expectations, it also needs to respect the needs ofsupporting organizations to manage their own affairs. That is, thetext above does not suggest that the IETF should micro-manage thefinancial affairs of supporting organizations.However, the very clear requirement is for clarity in thedistribution of rights, responsibilities, and accountability in those relationships. The usual mechanism for documenting such clarity isin contract form. Thus, the IETF needs to have clear contractualrelationships with the organizations supporting basic services,including meeting organization, secretarial services, IT services,etc.3.1.4. Flexibility in Service ProvisioningThe IETF needs to be able to raise money for, and fund thedevelopment of, additional services as appropriate. This includesthe development of tools for participants, repository management,etc.3.1.5. Administrative EfficiencyThe IETF’s needs should be met with the minimum of overhead. Thisimplies that there needs to be the possibility of combining workefforts where appropriate, and generally avoiding duplication ofeffort.IAB Advisory Committee Informational [Page 11]3.2. StewardshipThe requirements described below focus primarily on the needs of the IETF administration on a day-to-day basis. However, responsiblemanagement includes stewardship for future IETF work.3.2.1. Accountability for ChangeThe IETF needs to be responsible for changing its administrativestructure to meet the community’s evolving needs. As such, theadministration needs to remain uniquely accountable to the IETFcommunity.This also means that the distribution of responsibilities must beclear to the IETF community, in order to permit it to comment oncurrent actions or future plans, and also to allow it to take action when its needs are not being adequately addressed.An implication of this is that responsibility for financialmanagement within the IETF needs to sit with individuals who areaccountable within the IETF organizational structure.3.2.2. Persistence and Accessibility of RecordsMuch of the work of the IETF is focused on reaching decisions anddeclaring closure. However, responsibility does not stop with thedeclaration of completion. There are any number of reasons thathistory must be adequately documented so that future work can review substantive records, and not rely on oral history.Therefore, the IETF needs to maintain and support the archiving ofall of its working documents in a way that continues to beaccessible, for all current and future IETF workers.3.3. Working EnvironmentPart of the job of administering the IETF is identifying and ensuring the continued support of the tools and working environment necessary to support the ongoing activity.3.3.1. Service AutomationWherever human judgment is not required in order to complete anaction, services should be automated to provide the most friction-free path and minimal delay in completing the action.IAB Advisory Committee Informational [Page 12]More processes could be accomplished without requiring humanjudgment. Wherever possible, these processes should be identified,clarified, and automated.Note that this is not intended to imply ALL processes should beautomated! Rather, by reducing the friction incurred in steps thatare truly mechanical, more time and energy will be available toproperly treat those that require individual judgment.3.3.2. ToolsWhether housed in an IETF-supported location or offered by individual contribution, the PROBLEM WG has identified the need for more toolsupport for working groups and specification development. The IETFneeds to be able to identify, develop and support an adequately rich, consistent set of tools for getting the standards work done.4. Advisory Committee AdviceThe Advisory Committee discussed the material and observations,described in this document, at great length. To the AdvComm, itappeared clear that some level of IETF administration organizational change is needed to address the stressors and meet all of therequirements outlined in Section 3.4.1. Proposed: (Single) Formalized IETF Organizational EntityIn order to ensure an IETF structure that is capable of meeting therequirements outlined above, the AdvComm recommends that the IETF be more formally organized. This would allow the IETF to take fullresponsibility for, and management of, the resources required toaccomplish its work (as described in Section 3.1), provide andmaintain the necessary work environment for current work (asdescribed in Section 3.3), and provide appropriate stewardship of the institutional information required for all aspects of current andfuture work of the organization (as described in Section 3.2).Some proposed models for establishing such a formalized effort aredescribed in the following sections. Some of the key expectations,irrespective of the final implementation of formalism, are:o the administration of the IETF would remain accountable to theIETF leadership and community; the goal would be to ensure thatlines of responsibility and accountability were clearer;o this formalized IETF would be responsible for managing financialresources (revenue and expenses) directly;IAB Advisory Committee Informational [Page 13]o this formalized IETF would be directly signatory to agreementswith other organizations, and would therefore be able to negotiate and administer any appropriate contracts;o however implemented, this would require a small staff complement(e.g., one full-time person) responsible to no other organization than the one chartered with the IETF’s mission;o nevertheless, it remains a non-goal to create an organizationalentity that exists simply for the purpose of continuing to exist. This should be executed with the minimum formality needed in order to address the identified requirements.4.1.1. Comments on the Necessity of this FormalizationAn important question is: what does this proposed formalizationprovide that cannot be provided by the status quo? The AdvCommbelieves that an appropriately implemented formalization of the IETF would permit the unification of the resource management, decisionmaking and stewardship that is imperative to providing clarity andensuring a viable future for the IETF. The AdvComm further believes that this is simply not possible to implement within the existingdistributed and informal arrangement of responsibilities.Naturally, the act of forming such an organization does notimmediately satisfy the requirements outlined in Section 3. It isnot a silver bullet. Changing the formal structure will not, forexample, change the financial status of the IETF. However, theAdvComm believes it would provide the necessary basis from which the required decisions could be made and acted upon.In short, the AdvComm believes that we first have to place theresponsibility for defining the IETF’s administrative environmentwith specific people who are accountable to the IETF community. Then these people can take the detailed decisions that will change theIETF’s administrative environment to fulfill its requirements.4.2. Possible StructuresSection 4.1 was deliberately vague on the nature of the formalorganizational entity that might provide the proper environment,focusing instead on the key components of any implementation of such a formalization, and how the formalization activity would address the requirements laid out in Section 3.IAB Advisory Committee Informational [Page 14]。

rfc3716.The IETF in the Large Administration and Execution

合集下载

因特网流协议

IPv6 演进技术要求基于 IPv6 段路由(SRv6)的 IP 承载网络-最新国标

中移动家庭网关终端技术规范v ()

imap rfc标准

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

IETF会议介绍

RFC1636

rfc相关设置及使用

rfc3326(The Reason Header Field for the Session Initiation Protocol (SIP))

rfc4716.The Secure Shell (SSH) Public Key File Format

文档推荐

最新文档

rfc3716.The IETF in the Large Administration and Execution

合集下载

因特网流协议

IPv6 演进技术要求 基于 IPv6 段路由(SRv6)的 IP 承载网络-最新国标

中移动家庭网关终端技术规范v ()

imap rfc标准

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

IETF会议介绍

RFC1636

rfc相关设置及使用

rfc3326(The Reason Header Field for the Session Initiation Protocol (SIP))

rfc4716.The Secure Shell (SSH) Public Key File Format

文档推荐

最新文档

IPv6 演进技术要求基于 IPv6 段路由(SRv6)的 IP 承载网络-最新国标