Routing Working Group
E831145
The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Routing WG | 1 |
| Routing Working Group canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9933472 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Routing Working Group Context triple: [RIPE community, hasWorkingGroup, Routing Working Group]
-
A.
Routing Area Working Group
The Routing Area Working Group is an Internet Engineering Task Force (IETF) group responsible for developing and maintaining standards and guidelines related to Internet routing technologies and protocols.
-
B.
RFC Series Working Group
The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
-
C.
Network Working Group
The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
-
D.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
E.
IPng Working Group
The IPng Working Group was an IETF group responsible for designing and standardizing IPv6 as the successor to IPv4.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Routing Working Group Target entity description: The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
-
A.
Routing Area Working Group
The Routing Area Working Group is an Internet Engineering Task Force (IETF) group responsible for developing and maintaining standards and guidelines related to Internet routing technologies and protocols.
-
B.
RFC Series Working Group
The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
-
C.
Network Working Group
The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
-
D.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
E.
IPng Working Group
The IPng Working Group was an IETF group responsible for designing and standardizing IPv6 as the successor to IPv4.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet governance body
ⓘ
RIPE community working group ⓘ |
| abbreviation |
Routing WG
ⓘ
linked to:
Routing Working Group
|
| aimsTo |
coordinate routing policies in the RIPE region
ⓘ
facilitate discussion on routing technologies ⓘ improve stability of Internet routing ⓘ promote best practices for routing ⓘ support deployment of secure routing mechanisms ⓘ |
| collaboratesWith |
RIPE NCC
ⓘ
other RIPE working groups ⓘ |
| communicationChannel | public mailing list ⓘ |
| decisionMakingProcess | community consensus ⓘ |
| focusesOn |
BGP
ⓘ
Internet routing policies ⓘ Internet routing practices ⓘ Internet routing technologies ⓘ inter-domain routing ⓘ routing policy coordination ⓘ routing security ⓘ |
| governanceModel | bottom-up ⓘ |
| hasParentOrganisation | RIPE community ⓘ |
| hasStakeholder |
Internet exchange points
ⓘ
linked to:
Internet peering
Internet service providers ⓘ RIPE NCC members ⓘ content networks ⓘ network operators ⓘ research networks ⓘ |
| holdsSessionAt |
RIPE Meetings
ⓘ
linked to:
RIPE Meeting
|
| languageOfWork | English ⓘ |
| operatesInRegion | RIPE NCC service region ⓘ |
| participationPolicy | open to anyone ⓘ |
| partOf | RIPE community ⓘ |
| produces |
best current practices
ⓘ
meeting minutes ⓘ presentations ⓘ recommendations ⓘ |
| scope |
operational
ⓘ
technical ⓘ |
| topic |
RPKI
ⓘ
address aggregation ⓘ interconnection ⓘ peering policies ⓘ route filtering ⓘ routing registries ⓘ |
| usesForum |
RIPE Meetings
ⓘ
linked to:
RIPE Meeting
mailing list ⓘ |
| website | https://www.ripe.net/participate/ripe/wg/routing ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Routing Working Group Description of subject: The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Routing Working Group