Resource details: AS number 4242420119

Resource nameAS number 4242420119
Resource label03fcde3197
Resource size2943 bytes
Owner keycb2d7f722703b9431399954e31dcced81a975ecb8224d939ec9e8ceccabd012f
Serial number1538911793 (2018-10-07 11:29:53)
Ownership transferany
Transfer chainThis resource has embedded transfer history data (112 bytes)
Raw dataView details
HistoryBrowse previous versions
StatusTransferable
Owner nameJRB0001-DN42
Import sourcedn42

Transfer chain

This resource contains embedded transfer history data.

Resource labelOwner keySerial numberData
AS number 4242420119cb2d7f722703b9431399954e31dcced81a975ecb8224d939ec9e8ceccabd012f1538911793 (2018-10-07 11:29:53)transfer to any

Other data

datahash
'84a3b1641ef2077c742e4fc81e27dead'
dn42-data
array (
  'name' => 'AS4242420119',
  'aut-num' => 
  array (
    'aut-num' => 'AS4242420119',
    'as-name' => 'JRB0001',
    'admin-c' => 'JRB0001-DN42',
    'tech-c' => 'JRB0001-DN42',
    'mnt-by' => 'JRB0001-MNT',
    'remarks' => 
    array (
      0 => '',
      1 => 'This AS is open for new peerings provided that the following requirements are met:',
      2 => '- At least two IPv6 or multiprotocol BGP sessions are required, IPv4 BGP sessions are optional.',
      3 => '- The contact informations in the registry must always be up to date. The tech-c and admin-c must respond within one week and must read the mailing list.',
      4 => '- The routing policy should be properly documented in the registry within one week after the peering is established.',
      5 => '- The peer AS must have at least one other transit and/or upstream peer.',
      6 => '- The peering must not be down for longer periods of time. Foreseeable downtime of more than one day should be coordinated.',
      7 => '- The round trip time between the border routers must be reasonable. This is not required for simple downstreams.',
      8 => '- Issues in the peer AS can result in the peering being disabled. If this is the case, the peer has to request the reactivation of the peering after all issues are resolved.',
      9 => 'Please contact the admin-c for peering requests and the tech-c for technical issues.',
      10 => '',
      11 => 'Well-known communities:',
      12 => 'RFC1997, RFC3765, RFC7999 and RFC8326 are implemented as described in the RFC. Routes with the BLACKHOLE community are redistributed to peers only if they implement the RFC7999 as well.',
      13 => 'Custom communities for traffic engineering:',
      14 => '- (4242420119, 0, p)       Do not announce to ASp.',
      15 => '- (4242420119, 1..16, p)   Prepend x times before announcing to ASp.',
      16 => 'Custom communities for debugging assistance:',
      17 => '- (4242420119, 1000, n)    Route entered AS4242420119 on node n.',
      18 => '- (4242420119, 2000, n)    Route left AS4242420119 on node n.',
      19 => '',
      20 => 'Please note that the registry data has to be up to date or your routes will fail the checks. Only strict ROA and basic path validation is performed at the moment but full path validation is planned for the future.',
      21 => '',
    ),
    'mp-import' => 
    array (
      0 => 'afi any.unicast from AS4242420119:AS-TRANSIT accept ANY',
      1 => 'afi any.unicast from AS4242420119:AS-PEER accept PeerAS',
      2 => 'afi any.unicast from AS4242420119:AS-DOWNSTREAM accept PeerAS',
      3 => 'afi any.unicast from AS4242420119:AS-UPSTREAM accept ANY',
    ),
    'mp-export' => 
    array (
      0 => 'afi any.unicast to AS4242420119:AS-TRANSIT announce ANY',
      1 => 'afi any.unicast to AS4242420119:AS-PEER announce AS4242420119',
      2 => 'afi any.unicast to AS4242420119:AS-DOWNSTREAM announce ANY',
      3 => 'afi any.unicast to AS4242420119:AS-UPSTREAM announce AS4242420119 AS4242420119:AS-DOWNSTREAM',
    ),
    'source' => 'DN42',
  ),
)