default search action
Brian Haberman
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2022
- [i28]Brian Haberman:
Control Messages Protocol for Use with Network Time Protocol Version 4. RFC 9327: 1-21 (2022) - 2021
- [c6]Na'Shea Wiesner, John Sheppard, Brian Haberman:
Using Particle Swarm Optimization to Learn a Lane Change Model for Autonomous Vehicle Merging. SSCI 2021: 1-8 - 2020
- [c5]Na'Shea Wiesner, John Sheppard, Brian Haberman:
Autonomous Vehicle Control Using Particle Swarm optimization in a Mixed Control Environment. SSCI 2020: 2877-2884 - [i27]Brian Haberman, Joseph Lorenzo Hall, Jason Livingood:
Structure of the IETF Administrative Support Activity, Version 2.0. RFC 8711: 1-22 (2020)
2010 – 2019
- 2018
- [c4]Stephyn G. W. Butcher, John W. Sheppard, Brian K. Haberman:
Comparative performance and scaling of the pareto improving particle swarm optimization algorithm. GECCO (Companion) 2018: 83-84 - 2017
- [i26]Ronald P. Bonica, Michelle Cotton, Brian Haberman, Leo Vegoda:
Updates to the Special-Purpose IP Address Registries. RFC 8190: 1-6 (2017) - 2016
- [i25]Robert Kisteleki, Brian Haberman:
Securing Routing Policy Specification Language (RPSL) Objects with Resource Public Key Infrastructure (RPKI) Signatures. RFC 7909: 1-14 (2016) - 2013
- [i24]Michelle Cotton, Leo Vegoda, Ronald P. Bonica, Brian Haberman:
Special-Purpose IP Address Registries. RFC 6890: 1-23 (2013) - 2012
- [j2]Brian Haberman, John W. Sheppard:
Overlapping particle swarms for energy-efficient routing in sensor networks. Wirel. Networks 18(4): 351-363 (2012) - 2010
- [c3]A. Roger Hammons Jr., Qinqing Zhang, Brian Haberman:
An Eavesdrop Vulnerability Analysis of Random Network Coding over Wireless Ad-Hoc Networks. WCNC 2010: 1-6 - [i23]Brian Haberman, David L. Mills:
Network Time Protocol Version 4: Autokey Specification. RFC 5906: 1-58 (2010) - [i22]Heiko Gerstung, Chris Elliott, Brian Haberman:
Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4). RFC 5907: 1-26 (2010) - [i21]Brian Haberman:
A Dedicated Routing Policy Specification Language Interface Identifier for Operational Testing. RFC 5943: 1-4 (2010)
2000 – 2009
- 2009
- [c2]A. Roger Hammons Jr., Qinqing Zhang, Brian Haberman:
On the Eavesdrop Vulnerability of Random Network Coding over Wireless Networks. ICDCS Workshops 2009: 201-207 - [i20]Julian Chesterfield, Brian Haberman:
Multicast Group Membership Discovery MIB. RFC 5519: 1-41 (2009) - 2008
- [i19]Brian Haberman, Robert M. Hinden:
IPv6 Router Advertisement Flags Option. RFC 5175: 1-7 (2008) - [i18]Brian Haberman, Jim Martin:
Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction. RFC 5186: 1-6 (2008) - 2007
- [i17]Brian Haberman, Robert M. Hinden:
IPv6 Router Advertisement Flags Option. RFC 5075: 1-7 (2007) - 2006
- [j1]Jack L. Burbank, Philip F. Chimento, Brian Haberman, William T. Kasch:
Key Challenges of Military Tactical Networking and the Elusive Promise of MANET Technology. IEEE Commun. Mag. 44(11): 39-45 (2006) - [i16]Brian Haberman:
IP Forwarding Table MIB. RFC 4292: 1-34 (2006) - [i15]Hugh Holbrook, Brad Cain, Brian Haberman:
Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast. RFC 4604: 1-11 (2006) - [i14]Bill Fenner, Haixiang He, Brian Haberman, Hal Sandick:
Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying"). RFC 4605: 1-12 (2006) - [i13]Matt Crawford, Brian Haberman:
IPv6 Node Information Queries. RFC 4620: 1-14 (2006) - 2005
- [i12]Michael Daniele, Brian Haberman, Shawn A. Routhier, Jürgen Schönwälder:
Textual Conventions for Internet Network Addresses. RFC 4001: 1-22 (2005) - [i11]Stephen E. Deering, Brian Haberman, Tatuya Jinmei, Erik Nordmark, Brian D. Zill:
IPv6 Scoped Address Architecture. RFC 4007: 1-24 (2005) - [i10]Robert M. Hinden, Brian Haberman:
Unique Local IPv6 Unicast Addresses. RFC 4193: 1-16 (2005) - [i9]Brian Haberman, Jim Martin:
Multicast Router Discovery. RFC 4286: 1-18 (2005) - 2004
- [i8]Pekka Savola, Brian Haberman:
Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. RFC 3956: 1-18 (2004) - 2003
- [i7]Brian Haberman:
Source Address Selection for the Multicast Listener Discovery (MLD) Protocol. RFC 3590: 1-6 (2003) - 2002
- [i6]Mike Daniele, Brian Haberman, Shawn A. Routhier, Jürgen Schönwälder:
Textual Conventions for Internet Network Addresses. RFC 3291: 1-20 (2002) - [i5]Brian Haberman, David Thaler:
Unicast-Prefix-based IPv6 Multicast Addresses. RFC 3306: 1-7 (2002) - [i4]Brian Haberman:
Allocation Guidelines for IPv6 Multicast Addresses. RFC 3307: 1-8 (2002) - 2001
- [c1]Lakshminath R. Dondeti, Brian Haberman, Haldon J. Sandick, Thomas Hardjono, Haixiang He:
MBA: A Tool for Multicast Billing and Accounting. ISCC 2001: 172-177 - [i3]Brian Haberman, Randy Worzella:
IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol. RFC 3019: 1-15 (2001) - 2000
- [i2]Mike Daniele, Brian Haberman, Shawn A. Routhier, Jürgen Schönwälder:
Textual Conventions for Internet Network Addresses. RFC 2851: 1-16 (2000)
1990 – 1999
- 1999
- [i1]Stephen E. Deering, William C. Fenner, Brian Haberman:
Multicast Listener Discovery (MLD) for IPv6. RFC 2710: 1-22 (1999)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-24 23:01 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint