Hi All,
Thanks a lot for the inputs,
Here are my thoughts on NIX Proposal
1) I am not proposing standardization in Circuit naming convention.
2) Verizon partners with 250 other network organizations globally (Both in the domestic US and internationally)
3) We receive maintenance notification emails in non-standard format by the carrier. (Attached 5 sample emails from different carriers globally)
4) NIX is a proposal to standardize the email format only, create Open API to generate and read such standardized emails.
5) Without standardization, these network/telecom organizations are relying on manual/rules/tools to process these emails and feed into internal systems.
Please let me know how to proceed.
------------------------------
Adithya Umakanth
Verizon Communications
------------------------------
Original Message:
Sent: Jan 21, 2019 03:10
From: Dave Milham
Subject: Proposal for NIX Protocol
WRT Network Carrier name
Carrier codes are issued and maintained by the ITU
See https://www.itu.int/oth/T0201
Data network Identifier DNIC in ITU Operational bulletins see https://www.itu.int/dms_pub/itu-t/opb/sp/T-SP-OB.714-2000-PDF-E.pdf
Int'l Leased circuit identifier structure is ITU M.1400 series see
https://www.itu.int/rec/T-REC-M.1400/en
Which is why I asked the question about X.790 which includes scheduled maintenance and was originally developed for int'l leased circuits.
------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum
Original Message:
Sent: Jan 16, 2019 10:24
From: Adithya Umakanth
Subject: Proposal for NIX Protocol
Hi All,
Following is a proposal on the NIX Protocol - Network Information Exchange Protocol. If the Open API community concur for the need, will step into the further process of documentation and API development. Please guide and let me know your feedback.
INTRODUCTION
The following document is the proposal for standardizing the maintenance activity related email communication between network companies. Globally network companies <g class="gr_ gr_53 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" id="53" data-gr-id="53">do</g> partner with other network carriers for capacity augmentation and riding services to the customers. During maintenance activities that could impact the circuits of partnered companies, the communication happens in nonstandard email format. Though automation and standardization are experimented by some carriers since no standardization is in place, adopting communication means as per one's practice would be very much challenging without standardization. Hence there is a lot of manual process in place to covert the nonstandard email format communication into digital records.
While standardizing identified following key important attributes in maintenance activity that could impact partner companies' associated circuits or NEs or customers.
- Reference ID à Unique reference ID to communicate with network carrier partner for further communication regarding the maintenance activity(s)
- Network Carrier name à Sending company name who is going to perform the maintenance activity(s) that could impact the email recipient network company
- Subject à A one-line brief summary of maintenance activity(s) going to be performed
- Start Date and time along with time zones (local and GMT) à A set of start dates with associated time and zones information (In case of multiple maintenance activities planned in various windows of different dates or only one date time and zone). Time zone should be mentioned in the local time zone (EST/PST/CST) where the maintenance activity is going to be performed along with GMT +/- hours. Format MM/DD/YYYY HH24:MI<g class="gr_ gr_71 gr-alert gr_gramm gr_inline_cards gr_run_anim Style replaceWithoutSep" id="71" data-gr-id="71">:SS</g>.sss <g class="gr_ gr_57 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" id="57" data-gr-id="57">XST</g>/GMT-5
- End Date and time along with time zones (local and GMT) à A set of corresponding end dates, time and zone for each start date. Format MM/DD/YYYY HH24:MI<g class="gr_ gr_72 gr-alert gr_gramm gr_inline_cards gr_run_anim Style replaceWithoutSep" id="72" data-gr-id="72">:SS</g>.sss <g class="gr_ gr_58 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" id="58" data-gr-id="58">XST</g>/GMT-5
- Outage window Duration à If Multiple start/end dates are given either single outage window for all maintenance activities included can be provided or provide a set that corresponds to an individual pair of start/end dates. Format HH:MI<g class="gr_ gr_73 gr-alert gr_gramm gr_inline_cards gr_run_anim Style replaceWithoutSep" id="73" data-gr-id="73">:SS.sss</g>
- Impact Duration à Actual impact duration for every corresponding start/end date. Format HH:MI<g class="gr_ gr_74 gr-alert gr_gramm gr_inline_cards gr_run_anim Style replaceWithoutSep" id="74" data-gr-id="74">:SS.sss</g>
- NE Type à On what type of network element the maintenance activity is going to be performed on. Ex: - Switch/Circuit/Router
- NE Details à List of impacted NEs. If there is a relation between the date window and NEs list, then have a set of sets corresponding to each start/end dates.
- Detailed work description à A full work description of the maintenance activity. Free flow text.
- Update Flag à Is this notification an update notification of the previous email? 0 à Not an update, 1à Postpone notification, 2à Prepone notification
- Emergency à Yes or No, generally for the notifications below 24 hrs lead time this flag will be enabled
- Severity à High/Medium/Low depends on multiple factors duration, number of circuits, impacted customer base
- URL info à Any extranet URL to login and see the maintenance activity details else N/A
- Location à Where is the maintenance activity happening? Could be different locations based on the NE presence.
- Maps info à A set of Maps location URLs or lat-long coordinates or N/A
- Contact info à Contact email and phone number about the maintenance activity
Sample <g class="gr_ gr_51 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" id="51" data-gr-id="51">Json</g> with Maintenance Activities
{
"RefID": {},
"CarrierName": {},
"Subject": {},
"Actvities": {
"Activity1": {
"ActivityID": {},
"StartDateTimeZone": {},
"EndDateTimeZone": {},
"OutageWindow": {},
"ImpactDuration": {},
"NEType": {},
"NEDetails": {},
"WorkDescription": {},
"Location": {},
"Severity": {}
},
"Activity2": {
"ActivityID": {},
"StartDateTimeZone": {},
"EndDateTimeZone": {},
"OutageWindow": {},
"ImpactDuration": {},
"NEType": {},
"NEDetails": {},
"WorkDescription": {},
"Location": {},
"Severity": {}
}
},
"UpdateFlag": {},
"Emergency": {},
"URL": {},
"MAPsInfo": {},
"ContactEmail": {},
"ContactPhone": {},
"ContactAddress": {}
}
------------------------------
Adithya Umakanth
Verizon Communications
------------------------------