Catherine, Trevor,

We are in an extreme hurry to meet 3GPP's Rel-16 dead-line. Also, they are 
rather formalistic in their WoW. I will use the link approved by TSC and point 
out specifically in my answer that it reference the version used in Frankfurt.
I hope this is OK.

BR, Magnus

Den 12 maj 2020 16:12 skrev "LOVETT, TREVOR J" <tl2...@att.com>:
I don’t know of a way to include both the commit ID and branch in the URL.  I 
could potentially create a tag and the URL can have the tag in it, but I don’t 
seem to have permission to do that so I’d need to figure out how to do that.

I will reiterate that the official 7.1.1 spec URL is 
https://github.com/onap/vnfrqts-requirements/blob/frankfurt/docs/Chapter8/ves7_1spec.rst<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_onap_vnfrqts-2Drequirements_blob_frankfurt_docs_Chapter8_ves7-5F1spec.rst&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=ba-4BtmCA2f3Yd1j0Ko1uPkZMwIXSHYE2ZGUycls7Bo&s=A7kb4kJ-cYAcO2NkKxLH6MarNgQ-HJZGD8uw0kWQvxg&e=>,
 and the contents will not change.  If I was to make a change, that would 
constitute a 7.1.2 or greater update.  This would result in me creating a new 
document and new URL as well as notifying 3GPP of such an update per our 
liaison agreement.

I feel the desire to point 3GPP at a specific revision is unnecessary.  Even if 
I were to change to that document, it would still contain the 7.1.1 spec and 
anyone viewing the ONAP documentation would see the latest update as 7.1.1.  
3GPP would simply be pointing at an “old version” of the 7.1.1.  Pointing 3GPP 
at a specific revision doesn’t really solve the issue of 7.1.1 changing without 
their knowledge – only proper management of the spec, communication, and proper 
versioning solve that.

If there remains a desire to still point at a revision, then let me know if the 
URL with the commit ID is not sufficient and I can try to figure out how to 
create tag like ves_7_1_1_frankfurt, and I will investigate further.

Thanks,

Trevor Lovett
Lead Member of Technical Staff
AT&T Labs, Operational Automation and Program Management

From: LEFEVRE, CATHERINE
Sent: Tuesday, May 12, 2020 7:32 AM
To: onap-tsc@lists.onap.org; LOVETT, TREVOR J <tl2...@att.com>; Magnus Buhrgard 
<magnus.buhrg...@ericsson.com>
Subject: RE: [onap-tsc] Proposed replies to 3GPP Liaison Statements addressed 
to ONAP

My apologies I have sent the e-mail too fast
Please read except as “even”

Even when you open the rst file
[cid:image001.png@01D6283A.AFDABAD0]

KR
Catherine

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> On Behalf Of Lefevre, 
Catherine
Sent: Tuesday, May 12, 2020 2:27 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; LOVETT, TREVOR J 
<tl2...@att.com<mailto:tl2...@att.com>>; Magnus Buhrgard 
<magnus.buhrg...@ericsson.com<mailto:magnus.buhrg...@ericsson.com>>
Subject: Re: [onap-tsc] Proposed replies to 3GPP Liaison Statements addressed 
to ONAP
Importance: High

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Magnus, Trevor,

Although the TSC agreed to the proposed replies to 3GPP.
There is still some concerns regarding the link.
The following link is an unique reference but it could be confusing since there 
is no real reference to the Frankfurt release
https://github.com/onap/vnfrqts-requirements/blob/05f26fac2b941513a7d0e856b99fd8c61d688299/docs/Chapter8/ves7_1spec.rst<https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_v1_url-3Fk-3D499dafef-2D173d4f71-2D499def74-2D86ee86bd5107-2Da171e6f3e3b7aa5a-26q-3D1-26e-3D64746985-2Dd576-2D44ca-2Da2fe-2D6f77173d4ddb-26u-3Dhttps-253A-252F-252Fgithub.com-252Fonap-252Fvnfrqts-2Drequirements-252Fblob-252F05f26fac2b941513a7d0e856b99fd8c61d688299-252Fdocs-252FChapter8-252Fves7-5F1spec.rst&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=g9LhwjMTPM4AuoWvYyDmqA&m=dSIRsgigILPK1XkO88_V3KdV6e3yBY25tIIHJDYLT-c&s=6Bq81LcGST815-mSIEa7QPkmRy3AFvBsxLlmIORNq_Y&e=>

Except when you open the rst file
[cid:image001.png@01D6283A.AFDABAD0]

Is there a way that we use the following link, including the name of ‘Release 
branch’ i.e. Frankfurt
https://github.com/onap/vnfrqts-requirements/blob/frankfurt/docs/Chapter8/ves7_1spec.rst<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_onap_vnfrqts-2Drequirements_blob_frankfurt_docs_Chapter8_ves7-5F1spec.rst&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=ba-4BtmCA2f3Yd1j0Ko1uPkZMwIXSHYE2ZGUycls7Bo&s=A7kb4kJ-cYAcO2NkKxLH6MarNgQ-HJZGD8uw0kWQvxg&e=>

But we add a tag so we can keep the uniqueness of the reference?

Best regards
Catherine


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#6354): https://lists.onap.org/g/onap-tsc/message/6354
Mute This Topic: https://lists.onap.org/mt/74053850/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to