thank you!
", "time": "2023-11-10T12:00:36Z"}, {"author": "Boris Khasanov", "text": "the sound from chairs mic is quite low for remote participants
", "time": "2023-11-10T12:02:45Z"}, {"author": "Lou Berger", "text": "is that better
", "time": "2023-11-10T12:03:06Z"}, {"author": "Lou Berger", "text": "please join us for joint minute taking: https://notes.ietf.org/notes-ietf-118-teas
", "time": "2023-11-10T12:03:19Z"}, {"author": "Lou Berger", "text": "the chairs mic is loud in the room
", "time": "2023-11-10T12:03:58Z"}, {"author": "Boris Khasanov", "text": "a bit better
", "time": "2023-11-10T12:04:31Z"}, {"author": "Lou Berger", "text": "how's scott's volume
", "time": "2023-11-10T12:07:40Z"}, {"author": "Boris Khasanov", "text": "low too
", "time": "2023-11-10T12:07:55Z"}, {"author": "Lou Berger", "text": "@meetecho, the mics are loud in the room, but low on-line
", "time": "2023-11-10T12:08:12Z"}, {"author": "Lorenzo Miniero", "text": "Heading there to check
", "time": "2023-11-10T12:08:39Z"}, {"author": "Lou Berger", "text": "thank you!
", "time": "2023-11-10T12:08:44Z"}, {"author": "Mohamed Boucadair", "text": "Last time there was a complaint about colors :-)
", "time": "2023-11-10T12:12:24Z"}, {"author": "Lou Berger", "text": "the colors don't mean anything anymore - look at the small text
", "time": "2023-11-10T12:12:54Z"}, {"author": "Lou Berger", "text": "how's the volume now?
", "time": "2023-11-10T12:19:25Z"}, {"author": "altanai", "text": "+1 \"enhanced\" is an undefined term
", "time": "2023-11-10T12:19:47Z"}, {"author": "Boris Khasanov", "text": "@Lou, the volume is just great
", "time": "2023-11-10T12:20:59Z"}, {"author": "Lou Berger", "text": "@meetecho, thank you!
", "time": "2023-11-10T12:22:21Z"}, {"author": "Lorenzo Miniero", "text": "Glad to be of help!
", "time": "2023-11-10T12:22:32Z"}, {"author": "Eduard V", "text": "NRP-based is better because it revels how it was \"enhanced\", more meaning
", "time": "2023-11-10T12:23:56Z"}, {"author": "Loa Andersson", "text": "how many documents would need to be changed if we change the name, any past wglc
", "time": "2023-11-10T12:25:36Z"}, {"author": "Tony Li", "text": "'Enhanced' is a content-free marketing term, just like 'new and improved'. The E in IETF is for Engineering. :-) This is not the IMTF.
", "time": "2023-11-10T12:26:05Z"}, {"author": "Vishnu Beeram", "text": "@Loa -- I don't believe there are any related documents that are past WGLC
", "time": "2023-11-10T12:29:04Z"}, {"author": "Vishnu Beeram", "text": "Is there a recommendation of what the scheme in uri needs to be (for IETF yang models)?
", "time": "2023-11-10T12:33:52Z"}, {"author": "Mohamed Boucadair", "text": "this was listed in Dhruv slides: ongoing 8407bis
", "time": "2023-11-10T12:34:35Z"}, {"author": "Lou Berger", "text": "see https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-03
", "time": "2023-11-10T12:35:20Z"}, {"author": "Vishnu Beeram", "text": "@Med, @Lou -- Thanks!
", "time": "2023-11-10T12:36:05Z"}, {"author": "Italo Busi", "text": "For TE topology JSON there are examples in the TNBI DT I-D in CCAMP WG
", "time": "2023-11-10T12:36:46Z"}, {"author": "Italo Busi", "text": "https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-transport-nbi-app-statement
", "time": "2023-11-10T12:37:11Z"}, {"author": "Dhruv Dhody", "text": "A quick check but this draft has all the same URI problem
", "time": "2023-11-10T12:43:31Z"}, {"author": "Loa Andersson", "text": "draft-ietf-teas-rfc8776-update, I'm sure how \"update\" and \"bis\" are used, I thought \"update\" was a document that leaves the original document in force, while a bis replaces it. Correct?
", "time": "2023-11-10T12:46:16Z"}, {"author": "Lou Berger", "text": "correct
", "time": "2023-11-10T12:46:35Z"}, {"author": "Jie Dong", "text": "As I mentioned on the mail list, IETF has many WG documents /RFCs using enhanced XXX.
", "time": "2023-11-10T12:48:06Z"}, {"author": "Italo Busi", "text": "Loa Andersson said:
\n\n\ndraft-ietf-teas-rfc8776-update, I'm sure how \"update\" and \"bis\" are used, I thought \"update\" was a document that leaves the original document in force, while a bis replaces it. Correct?
\n
It is a bis but the name update in the I-D name is historical since we were not sure it would have been a -bis when the document was adopted as WG draft
", "time": "2023-11-10T12:49:07Z"}, {"author": "Loa Andersson", "text": "since it obsoletes rfc8776, it should be a bis
", "time": "2023-11-10T12:50:06Z"}, {"author": "Lou Berger", "text": "that's what the draft says: Obsoletes: 8776 (if approved)
", "time": "2023-11-10T12:51:07Z"}, {"author": "Lou Berger", "text": "the finle name is historc, as italo says
", "time": "2023-11-10T12:51:22Z"}, {"author": "Jie Dong", "text": "The term \"enhanced VPN\" shows it provides enhanced characteristics comparing to traditional VPN services. It is not the intention to expose the realization mechanisms in the name. Similarly, we don't call the traditional VPNs as \"LDP LSP based VPNs\"
", "time": "2023-11-10T12:52:24Z"}, {"author": "Boris Khasanov", "text": "IPSec VPNs ;)
", "time": "2023-11-10T12:53:48Z"}, {"author": "Loa Andersson", "text": "I can live with that, but it makes searching for bis's in the tracker harder and a name change and replaces is easy
", "time": "2023-11-10T12:54:13Z"}, {"author": "Lou Berger", "text": "I don't think anyone has had an issue with the filename to date. do you really think it's that important?
", "time": "2023-11-10T12:57:30Z"}, {"author": "Jie Dong", "text": "Boris Khasanov said:
\n\n\nIPSec VPNs ;)
\n
it is called secure VPN in some IETF documents
", "time": "2023-11-10T12:58:53Z"}, {"author": "Loa Andersson", "text": "I said that I can live with it
", "time": "2023-11-10T13:01:14Z"}, {"author": "Lou Berger", "text": "okay, thanks
", "time": "2023-11-10T13:01:45Z"}, {"author": "Mohamed Boucadair", "text": "We do use it in the realization model
", "time": "2023-11-10T13:09:18Z"}, {"author": "Mohamed Boucadair", "text": "so we need a means to convey it in the service request at the first place
", "time": "2023-11-10T13:09:32Z"}, {"author": "Vishnu Beeram", "text": "consistency with other service models would be good..
", "time": "2023-11-10T13:10:22Z"}, {"author": "Mohamed Boucadair", "text": "Agree. The document is getting more stable. Thank you the team!
", "time": "2023-11-10T13:13:17Z"}, {"author": "Lou Berger", "text": "I'm not sure how the \"green\" option works, so may need a chnage that implements the intent
", "time": "2023-11-10T13:13:22Z"}, {"author": "Dhruv Dhody", "text": "Thanks Med for all your help!
", "time": "2023-11-10T13:15:56Z"}, {"author": "Joel Halpern", "text": "I don't know what the right limit is, but I suspect that an IP network trying to use thousands of NRPs is likely to operate in ways other than those intended by the operator.
", "time": "2023-11-10T13:23:55Z"}, {"author": "Dhruv Dhody", "text": "<PCE-WG co-chair hat> The same applies to PCEP I-D as well, so looking forward to feedback from TEAS
", "time": "2023-11-10T13:27:57Z"}, {"author": "Abdussalam Baryun", "text": "many rfcxxx, i hope we delete these method of title
", "time": "2023-11-10T13:28:25Z"}, {"author": "Italo Busi", "text": "Maybe we need to get an early RFC number allocation :smile:
", "time": "2023-11-10T13:29:35Z"}, {"author": "Dhruv Dhody", "text": "@italo might be possible, worth checking with RPC
", "time": "2023-11-10T13:31:31Z"}, {"author": "Dhruv Dhody", "text": "usually number gets reserved when RPC starts editing the I-D in RFC editor queue
", "time": "2023-11-10T13:32:11Z"}, {"author": "Abdussalam Baryun", "text": "@Italo, using maybe RFC(to be confirmed) RFC(TBC)
", "time": "2023-11-10T13:32:15Z"}, {"author": "Vishnu Beeram", "text": "@Italo -- dont think having a number in there would make it less cumbersome (unfortunately)..
", "time": "2023-11-10T13:33:00Z"}, {"author": "Lou Berger", "text": "I suggest using RFC XXXX in references to the RFC and \"Network Slices\" and \"Network Slices Using IETF Technologies\" when referring to the slices that we work on in the IETF
", "time": "2023-11-10T13:33:01Z"}, {"author": "Lou Berger", "text": "I sent specific changes to the scalability document to the list
", "time": "2023-11-10T13:33:26Z"}, {"author": "Lou Berger", "text": "In other words do NOT do s/IETF Network Slices/RFC XXXX Networkslices/g
", "time": "2023-11-10T13:34:48Z"}, {"author": "Lou Berger", "text": "[speaking as contributor]
", "time": "2023-11-10T13:36:23Z"}, {"author": "Jie Dong", "text": "Thanks Lou, will consider to update that in the draft
", "time": "2023-11-10T13:39:30Z"}, {"author": "Abdussalam Baryun", "text": "@Lou, ok I understand, thanks
", "time": "2023-11-10T13:39:46Z"}, {"author": "Jie Dong", "text": "Joel Halpern said:
\n\n\nI don't know what the right limit is, but I suspect that an IP network trying to use thousands of NRPs is likely to operate in ways other than those intended by the operator.
\n
Yes. we may give examples of NRP realizations at different scales: 10, 100, 1000,...
", "time": "2023-11-10T13:43:57Z"}, {"author": "Abdussalam Baryun", "text": "I think you need to contact with C. Perkins
", "time": "2023-11-10T13:46:01Z"}, {"author": "Abdussalam Baryun", "text": "He is the one that is assigned I think for 3GPP
", "time": "2023-11-10T13:46:15Z"}, {"author": "Abdussalam Baryun", "text": "from IETF side
", "time": "2023-11-10T13:46:45Z"}, {"author": "Abdussalam Baryun", "text": "@WG_chair, and WG_ADs, is what I said correct or
", "time": "2023-11-10T13:47:33Z"}, {"author": "Abdussalam Baryun", "text": "not?
", "time": "2023-11-10T13:47:42Z"}, {"author": "Lou Berger", "text": "the information is available at https://www.ietf.org/about/liaisons/
", "time": "2023-11-10T13:48:35Z"}, {"author": "Vishnu Beeram", "text": "@Abdussalam -- Charles Eckel (see the link provided by Lou) helped us send the liaison to 3GPP..
", "time": "2023-11-10T13:50:35Z"}, {"author": "Abdussalam Baryun", "text": "@Lou and Vishnu, the authors need to know that, they did not get respond yet
", "time": "2023-11-10T13:51:31Z"}, {"author": "Abdussalam Baryun", "text": "within there presentation they said that no one responded to them so they don't know
", "time": "2023-11-10T13:53:18Z"}, {"author": "Abdussalam Baryun", "text": "that link contacts
", "time": "2023-11-10T13:53:49Z"}, {"author": "Abdussalam Baryun", "text": "If they don't get respond within a week, the IETF chair can help
", "time": "2023-11-10T13:55:33Z"}]