Thaler, David

RFCs Publications

Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
Voice:+1 425 703 8835
Fax:
Email: dthaler@microsoft.com
Web:

Chair, behave, Behavior Engineering for Hindrance Avoidance. IETF working group, Transport area.

Chair, malloc, Multicast-Address Allocation. IETF working group, Transport area. Concluded July 2003.

Chair, pcp, Port Control Protocol. IETF working group, Internet area.


RFCs:

[RFC 2117] Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification.

[RFC 2362] Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification.

[RFC 2667] IP Tunnel MIB.

[RFC 2715] Interoperability Rules for Multicast Routing Protocols.

[RFC 2776] Multicast-Scope Zone Announcement Protocol (MZAP).

[RFC 2908] The Internet Multicast Address Allocation Architecture.

[RFC 2909] The Multicast Address-Set Claim (MASC) Protocol.

[RFC 2932] IPv4 Multicast Routing MIB.

[RFC 2933] Internet Group Management Protocol MIB.

[RFC 2934] Protocol Independent Multicast MIB for IPv4.

[RFC 2991] Multipath Issues in Unicast and Multicast Next-Hop Selection.

[RFC 3306] Unicast-Prefix-based IPv6 Multicast Addresses.

[RFC 3559] Multicast Address Allocation MIB.

[RFC 3678] Socket Interface Extensions for Multicast Source Filters.

[RFC 3913] Border Gateway Multicast Protocol (BGMP): Protocol Specification.

[RFC 4087] IP Tunnel MIB.

[RFC 4191] Default Router Preferences and More-Specific Routes.

[RFC 4214] Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).

[RFC 4311] IPv6 Host-to-Router Load Sharing.

[RFC 4389] Neighbor Discovery Proxies (ND Proxy).

[RFC 5214] Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).

[RFC 5218] What Makes for a Successful Protocol?

[RFC 6034] Unicast-Prefix-Based IPv4 Multicast Addresses.


Publications:


RFCs Publications