Login

AS47184 TOUIX-AS France-IX Toulouse Previously known as TOUIX/TOUlo...



Loading

AS MEMBERSHIP

AS47184 is a member of the following AS sets:

AUTONOMOUS SYSTEM

AS47184 TOUIX-AS source:RIPE

aut-numAS47184
as-nameTOUIX-AS
descrFrance-IX Toulouse
descrPreviously known as TOUIX/TOUlouse Internet eXchange
orgORG-TA434-RIPE
remarks-------------------------------------------------------------
remarksInformation: http://www.franceix.net/
remarksPeering requests: info@franceix.net
remarksMembers technical support: noc@franceix.net
remarks-------------------------------------------------------------
remarksThe following communities can be used by members on our Route-Servers:
remarks:
remarksCDN Control (handled by AS39801, connected to the RS) :
remarks40027:40000 - DO announce to Netflix OpenConnect Appliance in Marseille
remarks39801:990:0 - DO NOT announce to any local CDN cache
remarks39801:990:1 - DO NOT announce to Netflix OpenConnect Cache [Default]
remarks39801:990:2 - DO NOT announce to Microsoft/Azure Cache [Coming Soon]
remarks39801:991:0 - DO announce to all local CDN caches
remarks39801:991:1 - DO announce to Netflix OpenConnect cache (and add 40027:40000)
remarks39801:991:2 - DO announce to Microsoft/Azure Cache [Coming Soon][Def*]
remarks[Def*] - Default behaviour, with a few exceptions
remarks-------------------------------------------------------------
remarksLarge BGP communities (RFC8092) :
remarksRFC8092 communities ("Large" BGP communities) are the preferred way
remarksof signalling between peers and the RS. Prefer using them !!!
remarks:
remarksCommunities handled by the RS (peers can set on routes announced to the RS):
remarks47184:0:0 = Do not send route to any peer unless explicitly signaled
remarks47184:0:peeras = Do not send route to this peer AS
remarks47184:1:0 = [DEFAULT] Send route to all peers
remarks47184:1:peeras = Send route to this peer AS (if 47184:0:0 specified)
remarks47184:101:peeras = Prepend 1x to this peer AS
remarks47184:102:peeras = Prepend 2x to this peer AS
remarks47184:103:peeras = Prepend 3x to this peer AS
remarks47184:901:peeras = Set MED to 50 for this peer AS
remarks47184:902:peeras = Set MED to 100 for this peer AS
remarks47184:903:peeras = Set MED to 200 for this peer AS
remarks:
remarksCommunities set by the RS (on routes peers receive):
remarks47184:1000:1 = RPKI : Valid ROA (ROA Valid)
remarks47184:1000:2 = RPKI : No ROA Present (RPKI Unknown)
remarks47184:1001:1 = IRR Valid (Origin in AS-Set and route object present)
remarks47184:1001:6 [*] = No IRR route object for prefix
remarks:
remarksCommunities for filtered routes, only visible on looking-glass:
remarks(routes tagged with these communities are NOT re-announced to RS peers)
remarks47184:1000:4 = RPKI Invalid
remarks47184:1001:4 = IRR Invalid/NotFound
remarks47184:1001:5 = IRR NotFound - Origin AS not in peer's AS-Set
remarks47184:1101:9 = FILTERED : IRR Invalid/NotFound
remarks47184:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
remarks47184:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
remarks47184:1101:13 = FILTERED : RPKI Invalid
remarks47184:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
remarks:
remarks[*] = A route without a valid IRR route object is only re-announced if:
remarks- the origin AS is in the peer's AS-Set
remarks- AND there is a VALID ROA for the origin AS
remarks-------------------------------------------------------------
remarksLegacy/"standard" BGP communities (RFC1997):
remarksRFC1997 BGP communities are still accepted, but their use will be
remarksreduced progressively. Please use RFC8092 "Large" communities instead.
remarks:
remarks0:peer-as = Do NOT send route to this peer as
remarks0:47184 = Do NOT send route to any peer
remarks47184:peer-as = DO Send route to this peer as
remarks47184:47184 = DO Send route to all peers [Default]
remarks:
remarks65101:peer-as = Prepend 1x to this peer
remarks65102:peer-as = Prepend 2x to this peer
remarks65103:peer-as = Prepend 3x to this peer
remarks65201:peer-as = Set MED 50 to this peer
remarks65202:peer-as = Set MED 100 to this peer
remarks65203:peer-as = Set MED 200 to this peer
remarks:
remarksThe following communities are applied by the route-server:
remarks47184:64615 = Prefix received from a peer on RS1 Toulouse
remarks47184:64616 = Prefix received from a peer on RS2 Toulouse
remarks47184:64655 = Prefix received from a FranceIX Toulouse peer
remarks47184:65011 = Prefix is present in an AS's announced AS/AS-SET
remarks47184:65021 = Prefix is not present in an AS's announced AS/AS-SET (NOT re-announced)
remarks47184:65012 = Prefix has RPKI status: VALID
remarks47184:65022 = Prefix has RPKI status: INVALID (NOT re-announced)
remarks47184:65023 = Prefix has RPKI status: UNKNOWN
remarks:
remarks*************************************************************
remarks** All communities are evaluated on a "first match win" basis
remarks*************************************************************
remarksAll other BGP communities in the public range
remarks(1-64495:x, 1-64495:x:y) and (131072-4199999999:x:y)
remarkswill be preserved and passed along by the route-servers
remarks-------------------------------------------------------------
remarksWell-known communities are propagated to all peers
remarks65535:666 = BLACKHOLE [RFC7999] - interpreted
remarksmore details at https://www.franceix.net/en/technical/blackholing/
remarksAll other well-known communities are NOT interpreted and passed along to peers
remarks-------------------------------------------------------------
remarksYou can filters prefixes with our AS-SET :
remarksAll members AS-SETs : AS-FRANCEIX-TLS
remarksAll members AS List : AS-FRANCEIX-TLS-LIST
remarksRoute-Servers members AS-SETs : AS47184:AS-MEMBERS
remarksRoute-Servers members AS List : AS47184:AS-MEMBERS:AS-TLS-RS
remarksPlease make sure to have at least one of theses lines in your aut-num object :
remarksexport: to AS47184 announce ASxxxx
remarksexport-via: AS47184 to AS-ANY announce ASxxxx
remarksexport-via: afi ipv6.unicast AS47184 to AS-ANY announce ASxxxx
remarksmp-export: afi ipv4.unicast,ipv6.unicast to AS47184 announce ASxxxx
remarks(ASxxxx can be your ASN or your AS-SET)
remarks-------------------------------------------------------------
remarksRoutes rejected:
remarks- Prefix too short : IPv4 :
remarks- Prefix too long : IPv4 : >/24, IPv6 : >/48
remarks- RFC5735 prefixes for IPv4 (includes RFC1918, RFC6598, and others)
remarks- RFC5156 prefixes for IPv6
remarks- RFC6996 - routes containing private ASNs in path
remarks- RPKI Invalid - routes having ROAs, and no ROA matches the announce
remarks- IRR AS Invalid - routes whose origin is NOT in Peers AS-Set
remarks- Invalid origin - routes that have NO valid ROA and NO matching IRR route object
remarks- routes where next_hop != announcing_peer
remarks- routes where first_ASN != peer_ASN
remarks- routes already having the OTC attribute (RFC9234) set
remarks-------------------------------------------------------------
remarksWe support ADD-PATHS. If negotiated via BGP, you will receive extended NLRI.
remarksWe support RFC9234 - our role is RS_Server.
remarksWe set the OTC attribute
remarksIf you implement RFC9234 your role will be RS_Client
remarks-------------------------------------------------------------
remarks==PEERS==
importfrom AS47184:AS-MEMBERS:AS-TLS-RS accept AS47184:AS-MEMBERS
exportto AS47184:AS-MEMBERS:AS-TLS-RS announce AS47184:AS-MEMBERS
remarks==END PEERS==
admin-cDUMY-RIPE
tech-cDUMY-RIPE
statusASSIGNED
mnt-byRIPE-NCC-END-MNT
mnt-byMNT-FRANCEIX
mnt-byTOUIX-MNT
notifynetwork@franceix.net
created2009-09-24T08:55:05Z
last-modified2025-10-03T15:27:42Z
sourceRIPE
sponsoring-orgORG-FISS1-RIPE
remarks****************************
remarks* THIS OBJECT IS MODIFIED
remarks* Please note that all data that is generally regarded as personal
remarks* data has been removed from this object.
remarks* To view the original object, please query the RIPE Database at:
remarks* http://www.ripe.net/whois
remarks****************************

REGISTERED ROUTES

table

%No entries found for the selected source(s).

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.