[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: [T1M1ALL] [Fwd: tML/XML Status in T1M1]



FYI

Bert 

-----Original Message-----
From: Michael Fargano [mailto:mfargan@qwest.com]
Sent: woensdag 31 juli 2002 23:10
To: T1M1 ALL; T1 T1Email
Subject: [T1M1ALL] [Fwd: tML/XML Status in T1M1]


Folks:

Just FYI - I pulled together this brief status report on "tML in T1M1" for a
colleague in TCIF/ESOC for him to share in TCIF/ESOC as needed.

Mike

--
-------------------------------------------------------------------
Mike Fargano
Industry Standards Coordinator
Qwest Emerging Technologies
Email: mfargan@qwest.com
Phone: 303-541-5141
Numeric Pager (toll-free): 877-433-1561
Text Pager - 2-Way Short Message - Email: 8774331561@skytel.com
Text Pager - Web Based: 8774331561 on the www.skytel.com web-site
Fax: 303-541-5351

----------Original Message-----
From: Michael Fargano [mailto:mfargan@qwest.com]
Sent: woensdag 31 juli 2002 22:42
To: John Sanclaria
Subject: tML/XML Status in T1M1 - OSS Interconnection


John:

Per discussion, the T1M1 tML (XML based Telecom Markup Language) status is as follows (as related to OSS
Interconnection):

- tML Framework ITU-T Recommendation (M.3030) is in the ITU-T approval process. The document is posted as
follows:  ftp://ftp.t1.org/T1M1/NEW-T1M1.0/2m100022.doc . Once M.3030 is approved, T1M1 will formulate a
Committee T1 tML Framework (ANSI) Standard (i.e., "delta doc" standards based on M.3030).

- The UOM (Unified Ordering Model - Access Ordering - ASR) Application  is moving along steadily - expecting a
Ballot in September/October 2002. See attached for a detailed status taken from the latest T1M1.5 report.

- The tML Trouble Administration Application is moving steadily. See attached for a detailed status taken from
the latest T1M1.5 report.

- The tML DSL Service Provisioning Application has been in Red Status (i.e., jeopardy) for some time (due to the
industry down turn). T1M1 will likely move this work to an inactive state soon. See
ftp://ftp.t1.org/T1M1/NEW-T1M1.0/2M100910.txt  for a detailed status report.

Feel free to share this with the folks in TCIF.

Mike Fargano
T1M1 Chair

--
-------------------------------------------------------------------
Mike Fargano
Industry Standards Coordinator
Qwest Emerging Technologies
Email: mfargan@qwest.com
Phone: 303-541-5141
Numeric Pager (toll-free): 877-433-1561
Text Pager - 2-Way Short Message - Email: 8774331561@skytel.com
Text Pager - Web Based: 8774331561 on the www.skytel.com web-site
Fax: 303-541-5351


************ UOM Status Taken from the Latest T1M1.5 Report  ************


1. Continued discussing UOM Vol. II working document, UOM Vol. II information model, and UOM-ASR Vol. III Schemas

- Agreement that the UOM Schemas follow the tML Framework (contribution 2m15063)
- Met with tML AHG, OBS and GTDD AHG

2. GTDD and tML AHG interim virtual meeting August 14th to discuss ways to create access databases from UOM
Schemas to help populate the GTDD

3. UOM Volume II (TCIF) and UOM Volume III (T1M1) Letter Ballot projected for September

4. Discussed UOM Vol. 4 (TCIF) related issues
- Same protocol stack as previously discussed, i.e. XML Body over TCP/IP, TLS and HTTP, SOAP
- TCIF Technology Support Committee should complete two documents in September:  Connectivity/Security (99016)
document and the XML transporter document


************ Trouble Admin Status Taken from the Latest T1M1.5 Report ************

Trouble Admin - Joint Meeting with TCIF:

- Discussions on SOAP being the protocol for transferring XML messages
-TCIF plans to make SOAP Header included in the envelope where URI represents the schema and code for the
operation
- Two choices discussed: define a generic set of operations similar to CMIP or let applications define what they
need. The second may be a preference for TCIF because each application may need different operations. No
conclusion reached. TCIF member plans to have a document for protocol profile in September.
- Need to decide once a choice is made, where the use of SOAP is to be documented assuming this is the selected
protocol for X interface
- Reviewed the output from interim meeting on the use cases and class definitions. Additional work to expand on
this draft
- Decision needed how to publish the output which is documented as html links
- Reviewed the input for a protocol to support general purpose paradigm (see M1-064) - further contributions
needed.
- An interim meeting is planned from July 29-31   to continue this effort and review the output of XML definition
based on agreements from interim meeting in May



-- 
!! This message is brought to you via the `nmrg' mailing list.
!! Please do not reply to this message to unsubscribe. To unsubscribe or adjust
!! your settings, send a mail message to <nmrg-request@ibr.cs.tu-bs.de>
!! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg.

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>