[03:25:17] AdrianFarrel joins the room [03:44:39] AdrianFarrel leaves the room [03:55:46] SoftgearKo joins the room [04:01:38] SoftgearKo leaves the room [04:01:39] elisa.bellagamba joins the room [04:01:59] AdrianFarrel joins the room [04:02:01] we are starting [04:02:28] Ciao Elisa [04:02:42] ciao :-) [04:02:43] shamus joins the room [04:03:11] moving the supplementar information to the wg wiki [04:03:47] document status stored on trac system [04:04:36] easier to see the status update [04:05:02] liaison also stored via trac [04:05:12] wiki open for modification to everyone [04:05:17] login required [04:06:27] Chairs thanked Elisa for doing the jabber room [04:06:37] (Elisa too modest to record this) [04:06:44] :-) [04:07:17] going through the documents in last call [04:08:25] there also some other WG draft not in agenda (G694 LABEL AND ETHRNET PROVIDED REQUIREMENTS, sorry for the capital letters) [04:08:53] discussions about these two documents can be done via the mailing list [04:11:25] milestones are to be discussed tomorrow as part of the agenda [04:11:59] showing communications with: ITU-T, OIF, MEF and IEEE [04:12:21] please use the ccamp list for comments [04:12:42] hide.zebra joins the room [04:12:56] th ason routing list has been closed [04:13:29] listing other "errata" [04:14:07] how many trace object can be present on a tracemonitor message? [04:14:33] (as part of errata on RFC 4207) [04:15:13] asking for comments on the agenda [04:15:30] first speaker [04:15:34] L. ONG [04:15:45] itu-t/oif report [04:16:13] couple of slides on oif and several from itu (malcom and kam) [04:17:00] OIF is focused on phy link specification, routing, multilayer, pce, OTN extensions [04:17:12] 2 liaisons: [04:17:36] 1- questions on restoration triggers an errors code [04:18:01] 2- follow up draft for more detailed input to caamp [04:19:50] --- ITU-T SG 15: Q14--> reviosion of recommendation G.7713 [04:20:14] ALSO CONSENTED NEW REC. g.7716 [04:21:02] sg15 liaiaon on OTNT work plan [04:21:50] Q6 --> liaison on lambda switch capable equipment (thanks ccamp for its liasison) [04:22:44] also provides detailed comments and proposals regarding g.697, g.680 [04:23:14] ---- liaison on WSON impairments draft [04:23:45] definition of "black link"...do we have a common definition? [04:24:00] q12 --> initiated a work on architecture [04:24:28] aggressive target of consensus for june 2010 [04:25:03] --- liaison on OTN enhancements: new payloads and high order ODUs [04:26:49] change in direction on modeling for describing ODU as a single layer network [04:27:36] implication for the control plane: additional link information needed to carry (OTU rate, total number of TS available...) [04:28:03] Lou has a question on the OIF slide [04:29:20] lou in not sure on the issue raised regarting the extensions [04:30:22] lyndon --> code point should be agreed by people implementing them [04:30:35] shamus leaves the room [04:31:55] adrian --> ospf ason: ospf registry says that if you have an exp document, the code points should be taken from the esp range (IANA) [04:32:13] lou --> the definition of the exp has changed during the time [04:32:54] ----------------- [04:33:01] second presentation [04:33:20] G. Bernstein [04:33:23] And the point is that IANA is not allowed to record OSPF registrations for Experimental RFCs [04:33:41] Framework for GMPLS and PCE control of ... [04:34:51] relation to signal compatibility work [04:36:11] this document is going to last call [04:37:20] ------ presentation 2.B (still Bernstein) [04:37:40] information for RWA in WSON [04:38:07] going also to last call [04:38:17] --------------------- presentation 2.c [04:38:35] ccamp-RWA-encode [04:39:26] fmcway joins the room [04:39:33] showing the changing from previous version (some inconsistency) [04:40:01] added connectivity matrix [04:40:13] added E bit to the w. converter [04:40:19] going to last call [04:43:06] (huaway) -> they plan to update their draft introduction ... they're going to have 2 encoding drafts for reference... [04:43:09] (?) [04:43:21] ------------ pres 2.d [04:44:17] extend the gmpls/pce control plane [04:45:25] optical signal parameter/attributes [04:47:50] (huaway) = Young Lee [04:47:53] output constraints [04:48:43] chracterizing network element [04:49:01] hide.zebra leaves the room [04:49:09] networking scenarios & GMPLS implications [04:52:26] adopt this document as a CCAMP WG document [04:53:09] --------------- pres 2.e [04:53:24] sign ext for wavelength swith Opt netw [04:54:14] changed to address anything new about compatibility [04:55:02] signal attributes and processing [04:55:26] modulation type TLV, FEC Type TLV, regeneration Processing TLV [04:56:05] adopt as a WG document [04:56:19] and keep aligned with wson compatibility draft [04:56:30] revise encodings as necessary [04:56:56] Lou --> how much it will be impacted by the implementation of the other documents? [04:57:07] Greg --> not impacted [04:57:53] Lou --> better to defer the question and see where the other documents are going [04:58:52] Lou --> encourage people to discuss about this document on the list (even if it is an individual draft) [04:59:04] --------------- presentation 3 [04:59:07] Y.Lee [04:59:19] OSPF COMPATIBILLITY ... [04:59:53] Wson NE Characterization [05:00:35] required routing information [05:01:19] opn issue on highest lvel TLV [05:02:29] aadopt as CCAMP WG document, refine requirements and refine encoding details [05:03:13] Lou ask how many people have read / and how many are in favour to adopt the document [05:03:21] it will be confirmend on the list [05:03:49] -------------------------- pres 4 [05:03:54] G. Bernstein [05:04:01] "WSON impairments" [05:04:59] LouBerger joins the room [05:05:12] changes: small changes because they didn't get the infos from the lisison [05:05:56] next steps: update document based on the liaison, refine requirements and models [05:08:20] ------------------------pres 5 [05:08:28] Fatai Zhang [05:08:34] "OSPF ext for WSON" [05:08:58] no consideration for optical impairment [05:09:19] wson specifig infos [05:09:39] switch connectivity matrix / wavelength converter pool info [05:10:35] link sub-tlv: port wavelength restr, avail. wavelenght, shared backup wavelenghts [05:12:12] next steps: adopt as WG document, refine according to feedback, keep it consistent with the encoding draft [05:13:30] -------------------------------- pres 6 [05:13:35] FAtai [05:13:44] " OTN ... " [05:14:05] giving a background on G.709 [05:14:22] OTN layer network, mapping multiplexing [05:15:39] only focus listing all the important cases for tributary slot allocation [05:16:17] showing typical examples on connection management on OTN [05:19:10] implications for hierarchy with gmpls te [05:19:44] implications for the signalling: new traffic parameters, new label [05:20:23] implications for routing: extentions for multiplexing capability, TS granularity, link bw information [05:21:41] implications for auto-discovery: correlate the granularity of the TS, CORRELATE THE SUPPORTED lo odu signal type [05:22:07] implications for PCE: new signal type / related variable bw [05:23:08] next steps: move the cotent of g.sup43 in an appendix, put reference to g-709, continue discussion with ITU-T lisison to sg 15 [05:25:18] (zte) --> no automatic discovery in the data plane ... (?) [05:26:29] deborah --> we need to align with ITU-T, for example not using the multi layering approach...we should be careful on that [05:27:09] (fatai) --> the fault topology can follow the same model... [05:28:30] (eve) --> good idea the communication put in place with ITU-T, but no autoconfiguration in the 1709. Agree with both of them on having this consistency. [05:29:03] ------------------------------ pres 7 [05:29:06] D. Ceccarelli [05:29:26] "OSPF ext for GMPLS G.709" [05:29:39] At last, someone who speaks Italian [05:30:21] 3 points: OTN te INFO NEEDED FOR lo odu PATH COMPUTATION [05:30:35] - INTERFACE SWITCH. CAPABILITY [05:30:48] - compatibility consideration [05:31:41] point 1--> tributary slot type, TE link Type, LO ODU signal type [05:33:47] --> TE link total bw (to be distinguished between unboudled and boundled), TE link unreserved bw, max LSP bw [05:34:35] point 2 --> interface capability descriptor, showing the object picture [05:34:57] showing how the draft defines the switch cap. info [05:37:08] compatibility considerations: when a node receives a LSA with SC = 10 then ... [05:37:32] ( compatibility considerations:) --> legacy nodes [05:38:11] next steops: monitoring g.709, move non normative signal types to appendix, requesting feedbacks [05:38:26] ------------------------------ pres 8 [05:38:33] F. Zhang [05:38:53] "gmpls signalling ext for the evolving G.709 OTN control" [05:40:21] changes: modified the introduction, add note to explain that traffic parameters may be updated to support ODUflex connection [05:41:12] issues summary: how to support ODUflex control (part of the liaison), backward compatibility, tributary slots order [05:41:56] showing issue 1 (how to support ODU flex) on a picture [05:41:58] Daniel King joins the room [05:43:00] issue 2 (bk compatibility) [05:44:27] issue 3 --> showing a picture on tributary slot order [05:47:32] fmcway leaves the room [05:50:30] next steps: include property of ODUflex, remove non-normative thinkgs, refine it Lou --> very important that we are not getting into what's defined in the DP. The draft could be suitable to be brought in the FW document. Contact the authors of the fw document to integrate this material [05:50:57] Eve Varma confirms this I-D is limited to consented version of G.709 [05:51:24] (julien) -->wondering if Daniele was using a new swtc.cap. So the LSP sees 2 different sw.cap? [05:52:04] (julien) --> suggest that the 2 authors should agree and do some clarifications [05:52:22] ----------------------- presentation 9 [05:53:11] F.Zhang [05:53:15] " ..... " [05:53:59] interworking with RFC4328 [05:57:10] problem for other method [05:57:42] next step: futher discussion [05:58:39] (malcom) --> it seems that you have to understand the link before getting the topology [05:59:09] (malcolm) this proposal seems to allow link ends to advertise mismatched compatiblities [06:00:00] deborah propose to continue the discussion on the list [06:00:17] (malcom) --> misunderstanding on TS [06:00:44] trying to talk about links in terms of TS is wrong [06:01:03] session is finished, will continue tomottow morning [06:01:17] AdrianFarrel leaves the room [06:01:28] elisa.bellagamba leaves the room [06:02:22] LouBerger leaves the room [06:04:13] Daniel King leaves the room: http://xeus-messenger.blogspot.com/ [23:52:05] LouBerger joins the room [23:57:06] Daniel King joins the room