Protocol Distribution

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 147 Experts worldwide ranked by ideXlab platform

Cisco Systems - One of the best experts on this subject based on the ideXlab platform.

  • Mobile Node Identifier Option for Mobile IPv6 (MIPv6
    2014
    Co-Authors: Alpesh Patel, Cisco Systems, Mohamed Khalil, Haseeb Akhtar, K. Leung, K. Chowdhury
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain Name (FQDN), International Mobile Station Identifier (IMSI), and Mobil

  • Table Of Contents
    2014
    Co-Authors: C. Desanti, Cisco Systems
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2004). This document specifies the way of encapsulating IPv6 packets over Fibre Channel, and the method of forming IPv6 link-local addresse

  • Network Working Group Request for Comments: 5640 Category
    2009
    Co-Authors: Clarence Filsfils, P. Mohapatra, C. Pignataro, Cisco Systems
    Abstract:

    Load-Balancing for Mesh Softwires Payloads transported over a Softwire mesh service (as defined by BGP Encapsulation Subsequent Address Family Identifier (SAFI) information exchange) often carry a number of identifiable, distinct flows. It can, in some circumstances, be desirable to distribute these flows over the equal cost multiple paths (ECMPs) that exist in the packet switched network. Currently, the payload of a packet entering the Softwire can only be interpreted by the ingress and egress routers. Thus, the load-balancing decision of a core router is only based on the encapsulating header, presenting much less entropy than available in the payload or the encapsulated header since the Softwire encapsulation acts in a tunneling fashion. This document describes a method for achieving comparable load-balancing efficiency in a network carrying Softwire mesh service over Layer Two Tunneling Protocol- Version 3 (L2TPv3) over IP or Generic Routing Encapsulation (GRE) encapsulation to what would be achieved without such encapsulation. Status of This Memo This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as th

  • Network Working Group Request for Comments: 5640 Category
    2009
    Co-Authors: Clarence Filsfils, P. Mohapatra, C. Pignataro, Cisco Systems
    Abstract:

    Load-Balancing for Mesh Softwires Payloads transported over a Softwire mesh service (as defined by BGP Encapsulation Subsequent Address Family Identifier (SAFI) information exchange) often carry a number of identifiable, distinct flows. It can, in some circumstances, be desirable to distribute these flows over the equal cost multiple paths (ECMPs) that exist in the packet switched network. Currently, the payload of a packet entering the Softwire can only be interpreted by the ingress and egress routers. Thus, the load-balancing decision of a core router is only based on the encapsulating header, presenting much less entropy than available in the payload or the encapsulated header since the Softwire encapsulation acts in a tunneling fashion. This document describes a method for achieving comparable load-balancing efficiency in a network carrying Softwire mesh service over Layer Two Tunneling Protocol- Version 3 (L2TPv3) over IP or Generic Routing Encapsulation (GRE) encapsulation to what would be achieved without such encapsulation. Status of This Memo This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents in effect on the date of publication of this documen

  • Extensions to OSPF for Advertising Optional Router Capabilities
    2007
    Co-Authors: Acee Lindem, Naiming Shen, Rahul Aggarwal, Cisco Systems, Jp. Vasseur, Scott Shaffer
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The IETF Trust (2007). It is useful for routers in an OSPFv2 or OSPFv3 routing domain to know the capabilities of their neighbors and other routers in the routing domain. This document proposes extensions to OSPFv2 and OSPFv3 for advertising optional router capabilities. A new Router Information (RI) Link State Advertisement (LSA) is proposed for this purpose. In OSPFv2, the RI LSA will be implemented with a new opaque LSA type ID. In OSPFv3, the RI LSA will be implemented with a ne

Bernie Volz - One of the best experts on this subject based on the ideXlab platform.

  • Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients
    2006
    Co-Authors: Bernie Volz
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). The Dynamic Host Configuration Protocol (DHCP) provides a mechanism for host configuration that includes dynamic assignment of IP addresses and fully qualified domain names. To maintain accurate name-to-IP-address and IP-address-to-name mappings in the DNS, these dynamically assigned addresses and fully qualified domain names (FQDNs) require updates to the DNS. This document identifies situations in which conflicts in the use of fully qualified domai

  • The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option", RFC 4702
    2006
    Co-Authors: Bernie Volz, Y. Rekhter
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). This document describes a Dynamic Host Configuration Protocol for IPv4 (DHCPv4) option that can be used to exchange information about a DHCPv4 client’s fully qualified domain name and about responsibilit

  • Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option", RFC 4649
    2006
    Co-Authors: Bernie Volz, Status Of This Memo
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). This document specifies a new Dynamic Host Configuration Protocol for IPv6 (DHCPv6) option that can be used to exchange information about a DHCPv6 client’s Fully Qualified Domain Name (FQDN) and about responsibility for updating DNS resource records (RRs) related to th

Nicolas Williams - One of the best experts on this subject based on the ideXlab platform.

  • Using Generic Security Service Application Program Interface (GSS-API
    2010
    Co-Authors: Nicolas Williams
    Abstract:

    This document defines a new function for the Generic Security Service Application Program Interface (GSS-API), which allows applications to store delegated (and other) credentials in the implicit GSS-API credential store. This is needed for GSS-API applications to use delegated credentials as they would use other credentials. Status of This Memo This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as th

  • Using Generic Security Service Application Program Interface (GSS-API
    2010
    Co-Authors: Nicolas Williams
    Abstract:

    This document defines a new function for the Generic Security Service Application Program Interface (GSS-API), which allows applications to store delegated (and other) credentials in the implicit GSS-API credential store. This is needed for GSS-API applications to use delegated credentials as they would use other credentials. Status of This Memo This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents in effect on the date of publication of this documen

Y. Rekhter - One of the best experts on this subject based on the ideXlab platform.

  • Dynamic Updates in the Domain Name System (DNS UPDATE)", Work in
    2014
    Co-Authors: P. Vixie, S. Thomson, Y. Rekhter
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. The Domain Name System was originally designed to support queries of a statically configured database. While the data was expected to change, the frequency of those changes was expected to be fairly low, and all updates were made as external edits to a zone’s Master File. Using this specification of the UPDATE opcode, it is possible to add or delete RRs or RRsets from a specified zone. Prerequisites are specified separately from update operations, and can specify a dependency upon either the previous existence or nonexistence of an RRset, or the existence of a single RR. UPDATE is atomic, i.e., all prerequisites must be satisfied or else no update operations will take place. There are no data dependent error conditions defined after the prerequisites have been met. 1- Definitions This document intentionally gives more definition to the roles of "Master, " "Slave, " and "Primary Master " servers, and their enumeration in NS RRs, and the SOA MNAME field. In that sense, the following server type definitions can be considered an addendum to [RFC1035], and are intended to be consistent with [RFC1996]: Slave an authoritative server that uses AXFR or IXFR to retrieve the zone and is named in the zone’s N

  • The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option", RFC 4702
    2006
    Co-Authors: Bernie Volz, Y. Rekhter
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). This document describes a Dynamic Host Configuration Protocol for IPv4 (DHCPv4) option that can be used to exchange information about a DHCPv4 client’s fully qualified domain name and about responsibilit

K. Chowdhury - One of the best experts on this subject based on the ideXlab platform.

  • Mobile Node Identifier Option for Mobile IPv6 (MIPv6
    2014
    Co-Authors: Alpesh Patel, Cisco Systems, Mohamed Khalil, Haseeb Akhtar, K. Leung, K. Chowdhury
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain Name (FQDN), International Mobile Station Identifier (IMSI), and Mobil

  • Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", RFC 4283
    2005
    Co-Authors: Alpesh Patel, Cisco Systems, Mohamed Khalil, Haseeb Akhtar, K. Leung, K. Chowdhury
    Abstract:

    This document specifies an Internet standards track Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this Protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain Name (FQDN), International Mobile Station Identifier (IMSI), and Mobil

Related terms

Protocol Distribution - 15 days free trial to Access Experts & Abstracts