IP address of the network element to be represented in the ControlConstruct
Thorsten Heinze
Hi together,
during today’s "Architecture, Semantic and Behavior" (former DMIP) call we elaborated a proposal for facilitating reading the IP address of the management port of the network element from the modeling. (This is of particular interest in case a Mediator is between Controller and Device.)
Please, prepare for discussing the following proposal on the next 5G-xhaul call on Wednesday, 18th of November.
Ideally, we would decide about this proposal on the 5G-xhaul call on Wednesday, 25th of November.
Proposal:
It is proposed to complement the TR-545 DMIP with the following formulation:
The device shall automatically write the IP address of the management port into the ControlConstruct::extension[*] attribute of NameAndValue datatype.
Separate entries shall be generated for IPv4 and IPv6 addresses, if such addresses are supported by the device.
The NameAndValue::valueName attribute shall be filled with "neIpAddressV4", respectively "neIpAddressV6".
The NameAndValue::value attribute shall be filled with the IPv4, respectively IPv6 address.
The string of the IPv4 address shall be formatted according to the following pattern: '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}' + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])' + '(%[\p{N}\p{L}]+)?'
The string of the IPv4 address shall be formatted according to the following pattern: '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}' + '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|' + '(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}' + '(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))' + '(%[\p{N}\p{L}]+)?'
If you would like commenting, but are not able to join the calls, please feel free emailing me or Martin upfront.
Otherwise, see you at the calls.
Best regards,
Thorsten
PS: Whoever able to read this pattern stuff is very much invited to check, whether we are actually requesting for the correct thing.
Thorsten Heinze | Telefónica Germany GmbH & Co. OHG
Lead Access Network Design
Access Network Technology
Georg-Brauchle-Ring 50 80992 München
M +49 (0)176 2442 4852 | T +49 (0)89 2442 4852 | F +49 (0)89 2442 7268
thorste...@telefonica.com |
www.telefonica.de
Bitte finden Sie hier die handelsrechtlichen Pflichtangaben:
www.telefonica.de/pflichtangaben
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
Thorsten Heinze
*** Now, with corrected patterns. Many thanks to Michael J ***
Hi together,
during today’s "Architecture, Semantic and Behavior" (former DMIP) call we elaborated a proposal for facilitating reading the IP address of the management port of the network element from the modeling. (This is of particular interest in case a Mediator is between Controller and Device.)
Please, prepare for discussing the following proposal on the next 5G-xhaul call on Wednesday, 18th of November.
Ideally, we would decide about this proposal on the 5G-xhaul call on Wednesday, 25th of November.
Proposal:
It is proposed to complement the TR-545 DMIP with the following formulation:
The device shall automatically write the IP address of the management port into the ControlConstruct::extension[*] attribute of NameAndValue datatype.
Separate entries shall be generated for IPv4 and IPv6 addresses, if such addresses are supported by the device.
The NameAndValue::valueName attribute shall be filled with "neIpAddressV4", respectively "neIpAddressV6".
The NameAndValue::value attribute shall be filled with the IPv4, respectively IPv6 address.
The string of the IPv4 address shall be formatted according to the following pattern:
(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])
The string of the IPv4 address shall be formatted according to the following pattern:
((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))
If you would like commenting, but are not able to join the calls, please feel free emailing me or Martin upfront.
Otherwise, see you at the calls.
Best regards,
Thorsten
Thorsten Heinze | Telefónica Germany GmbH & Co. OHG
Lead Access Network Design
Access Network Technology
Georg-Brauchle-Ring 50 80992 München
M +49 (0)176 2442 4852 | T +49 (0)89 2442 4852 | F +49 (0)89 2442 7268
thorste...@telefonica.com |
www.telefonica.de
Bitte finden Sie hier die handelsrechtlichen Pflichtangaben:
www.telefonica.de/pflichtangaben