Person
John Scudder
BGP routing protocol engineer and standards contributor
What to know first
- Public roleBGP routing protocol engineer and standards contributorMedium confidence
- Country or regionUnited States and global Internet technical communityMedium confidence
- Source basisPublic directory evidenceMedium confidence
- Last verifiedJul 29, 2026High confidence
Basic information
- NameJohn ScudderHigh confidence
- Public roleBGP routing protocol engineer and standards contributorMedium confidence
- Country or regionUnited States and global Internet technical communityMedium confidence
- Last verifiedJul 29, 2026High confidence
Related entities, projects, and resources
- Editorial contextJohn Scudder and the BGP Session That Had to Declare Its Capabilities, Two routers may complete a TCP connection and still be unfit for the BGP job expected of them. One may understand an optional extension that the other has never implemented; both may understand it while only one admits support in the OPEN message; or an older peer may reject the very container used to describe extensions. The standards record shared by John Scudder turns that uncertainty into an exchange of evidence. Capability Advertisement lets novelty survive without making novelty compulsory, and it makes refusal visible when a missing feature is genuinely indispensable.Medium confidence
- Editorial contextJohn Scudder and the Standards Work Behind BGP Origin Validation and Routing Policy, John Scudder's public IETF record connects early network operations, BGP implementation, route-origin validation, bounded error handling, and route observability. The record matters because inter-domain routing is not made trustworthy by one database, one standards document, or one engineer. It becomes more accountable when resource records, protocol states, local policy, implementation behavior, and observable route changes can be compared without confusing any one layer for the whole Internet.Medium confidence