[ietf86-tech] peering info

[Geert Jan de Groot]

Hi guys,

> did you ever get a translation of the peering info? I can somewhat 
> divine the information, but a proper English translation would be preferred.

Maybe I can help, I worked in Germany for 3 years and I'm reasonably fluent..

Oh, BTW, I see that Ruedige Volk is in cc - Ruediger is old hat at IETF,
he is an excellent escalation path.
[personal comments are in square brackets - geertj]

Please do note about the requirement to put route objects in the
RIPE database.

Please ping me if you need help,

Geert Jan

- ---



>> *From: *AS3320-BGP4-Administration <cip-peer at nmc-m.dtag.de 
>> <mailto:cip-peer at nmc-m.dtag.de>>
>> *Subject: **IP-Transit National für IETF 87, InterContinental Hotel 
>> Berlin; 5903094341/100001*
>> *Date: *April 23, 2013 2:35:13 AM PDT
>> *To: *oliver.rabe at ihg.com <mailto:oliver.rabe at ihg.com>
>> *Cc: *jim at daedelus.com <mailto:jim at daedelus.com>, rv at nic.dtag.de 
>> <mailto:rv at nic.dtag.de>

Dear mister Rabe,

Please find enclosed the config information for your new connection
for the IETF-meeting 87 in Berlin:

Your IP:               193.159.164.162/29
Your BGP Neighbour:    193.159.164.161
Your IPv6:             2003:0:1004:8001::2/64
Your v6 BGP Neighbour: 2003:0:1004:8001::1
Your BGP Neighbour AS: 3320
Your AS:               56554
BGP MD5 Key:           WNL6aihK

Data for a service (disruption) call:

Our Router:        B-EC3
Our Interface:     GigabitEthernet0/5/0/2
Connection:        0203059-1-1
Line key:          442/T1K/302690-305000/10018

At this moment, we get the following IPv4-prefixes if we query 
your AS 56554 at the RIPE IRR:

members:        31.130.224.0/20         #1:
members:        31.133.128.0/18         #1:

For IPv6 we get the following data if we query 
your AS 56554 at the RIPE IRR:
mp-members:     2001:67C:1230::/46
#Counters       ??? prefixes    1 lines

Our incoming BGP filters do exact matches and do require registration of
route- and route6- objects for all prefixes we need to accept
[BE AWARE!! geertj]

Configuration for the ethernet port:

no negotiation auto
duplex full
speed 1000/ speed 100/ speed nonegotiate
[I'm not sure this is correct but this is what the original doc says - geertj]

IMPORTANT MESSAGE ABOUT PROVISIONING OF YOUR CIRCUIT:
The provisioning is done independently from this email.
The circuit should be available starting the official start of your agreement.
This email provides details about the IP-configuration of your router.
The circuit will be transferred [given] directly by "Leitungstechnik"
[Circuit technician - geertj] or the Telehouse.

###
Contact details:
* Configuration Center (Office days, Mo-Fr: 07:30AM till 5.00 PM German time)
* Configurationcenter: +49 731 6032-4770
* Email: cip-peer at nmc-m.dtag.de 

Please call in at least one day in advance, if possible.

###
Contact for disruptions after initial setup:

[national]
Network Operation Center (for disruptions after succesful initial setup) [24h/7
d]
* NOC-Hotline: 0800 6645467 oder 0731 6032 2453
  [0800 numbers are free but may not work from intl numbers - 
  I suggest you also write down +49 731 6032 2453 - geertj]
* Email: noc at telekom.de 

[international]
Network Operation Center (for disruptions after succesful initial setup) [24h/7
d]
* NOC-Hotline: +800 4722 4733 oder +49 69 20060 5575
* Email: INMC.Helpline at telekom.de 

###
Contact for planned maintenance work:

Change Management Center [24h/7d]
 * Maintenance-Hotline: +49 69 20060 3262
 * Email: RCP.Frankfurt at telekom.de 

#############################################################

- -- 
Kind regards

Thomas Miesbauer

Deutsche Telekom Technik GmbH
Network and Service Operations
Thomas Miesbauer
Specialist, configuration and operations
BICP - Broadband & IP Central Platformcontrol
Olgastr. 67, 89073 Ulm
+49 731 / 6032 - 4770 (Tel)
E-Mail: cip-peer at nmc-m.dtag.de 
http://www.telekom.de