RE: V7R1 Updated SSL Ciphers RFE Link please vote!

Larry:

With all due respect to the CAAC, that's what's broken not IBM. RFE
popularity came about in part because the CAAC did not communicate at all
let alone effectively and the process to put in a requirement was hopelessly
convoluted. It is at best a requirements black hole.

Fix the CAAC (at least the communications and responsiveness part) and it
might become relevant again. Then again the RFE cat is out of the bag, it
might be too late.

As to EOL on V7R1, IBM is pulling another V5R4 on us and it's going to get
ugly again. I thought they would have learned a lesson but apparently very
strong voices in the LUG keep IBM from doing the right thing.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Tuesday, December 20, 2016 11:09 PM
To: Midrange Systems Technical Discussion
Subject: Re: V7R1 Updated SSL Ciphers RFE Link please vote!

WE don't know what is required to support those new ciphers. Sure it sounds
easy because the support was in fact added to newer releases. One could
surmise that it should be 'simple' since it's very likely that the code
bases are fairly similar, possibly the same. IF that is the case then the
changes might not be difficult but that's merely step one.
Clearly they would need to do regression testing on all the ciphers. I can
only guess what that might entail but given what they do it's unlikely it's
a few tests and 'Good to go!' So expect the cost to be 'not insignificant.'

As to your suggestion about ending support. I have stated on this list and
elsewhere that I expect the EOS announcement to occur 'at any moment.' This
is purely my conjecture of course and frankly in this case I'm surprised
that it has not yet come. This is even worse because IBM publicly states and
I read it again on their webber even today that once announced the date will
be at least one year out.

I'm really OK with such an announcement because some people need a nudge. An
EOS date would be such a nudge! I just think it's the wrong time of year.

Problem NOW is they've really blown the deadline because if they announce
today NOBODY has time left in the year to add budget money for an upgrade in
2017!! They really needed to do that before end of Q3 at the latest perhaps
even earlier. It's doubtful I'm wrong on this point.

Also this happens to be a problem I personally see with this rapid switch
from the COMMON Requirements process to the RFE process. Now there is no
buffer nobody in the middle to both qualify and quantify the requirements as
well as lobby for them with IBM. Now it's the wild wild west of "Hey vote
for MY RFE Lobby Lobby Lobby!" when it's already too late to request them
for this release. I think something got broken here.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/20/2016 11:53 PM, Bradley Stone wrote:

I am honestly befuddled at the resistance from IBM and you to provide
what should be a "gimme" for a supported release.

If IBM doesn't want to do it, tell your "connections" to politely end
support for V7R1. Don't make customers go through submitting a
request and voting for it if it's not going to make one iota of
difference. This isn't a reality show. It's people trying to run their

businesses.

It doesn't matter how old it is. It's supported! And these updates
are required for business to operate with the current standards.

21 votes. That has to be a new record. :)

Brad
www.bvstools.com


On Tue, Dec 20, 2016 at 10:16 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

They are taking money for 'Support' but that support gets you i 7.1
or 7.2 or 7.3. Much like other vendors (e.g. Microsoft) who still
'supports' a release but no longer provides enhancements i 7.1 is in
that same mode. IBM has stated that no more TRs are coming for i 7.1.

I believe many would say that adding support for new things would be
called an enhancement. The current level of support is to fix broken
things. All the ciphers in place are not broken. There are new and
enhanced ciphers which IBM has not added.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/20/2016 11:05 PM, Evan Harris wrote:

Hi Larry

I get what you say, but they are still taking money for V7R1 support
(at least that's how my customers see it) so until they end of life
V7R1 they ought to do something.
I don't expect database enhancements but SSL Ciphers does seem a
reasonable ask.


On Wed, Dec 21, 2016 at 4:51 PM, DrFranken <midrange@xxxxxxxxxxxx>

wrote:

You do realize that i 7.1 is a six and a half year old release and
there

are already TWO subsequent releases which DO support these ciphers?

I for one do not expect IBM to spend tons of money supporting old
releases when there are many new features and functions being
requested every day.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/20/2016 10:37 PM, Bradley Stone wrote:

Doesn't surprise me at all. Why give customers what they want and

need.

How would that business plan ever succeed.

I miss my AS400. :)


On Dec 20, 2016 9:32 PM, "DrFranken" <midrange@xxxxxxxxxxxx> wrote:

I have been told by 'people who know such things' that "IBM has no
plans to move any of the EC Ciphers to 7.1"

I have asked for an official statement or link to a page that
states this publicly and will pass this along when I get it.


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.


On 12/20/2016 5:34 PM, Kevin Wright wrote:

Voted.

Regards,

Kevin Wright

Were up to 17. Thanks to everyone!

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD